Overture MCP – Release Notes (v0.1.7)

This release focuses on plan reliability, branch execution correctness, structured execution output, attachment UX, and stronger prompt consistency across all supported agents.

✅ What Was Fixed

1) submit_plan success criteria now follows rendered result (not strict XML validity)

When submit_plan is called, invalid XML characters can still appear during parsing.
Previously, this could return a failure response even when the plan rendered correctly on canvas, which caused agents to regenerate unnecessary plans.

Now fixed: if nodes render successfully, the response is treated as success (render-first criteria), even if non-blocking XML parse issues exist.

———

2) Structured node execution output + richer UI rendering

Execution output handling was upgraded from plain text display to structured XML parsing for richer post-node summaries.

Implemented improvements include:

• Overview summary of what was done
• Structured categories for:
  • Files changed (with line add/remove info)
  • Files created
  • Files deleted
  • Packages installed
  • MCP setup actions
  • Web searches
  • Tool calls
  • Preview URLs
  • Notes
• Expandable UI sections for each category
• Prompt updates so agents format execution output in the expected structured XML style

———

3) Branch requirements now exclude unselected branch-only required fields

If a required field belongs to a branch path the user did not select, it should not block approval.

Now fixed: required field validation/checklist only enforces active/selected path requirements.

———

4) Branch flow bug fixed (removed unnecessary empty branch-selector node behavior)

Branch rendering/execution flow was corrected to avoid unnecessary “empty decision step” interruptions.

Correct flow behavior is now:

• node_1 → (node_2_a or node_2_b) → node_3

Instead of:

• node_1 → branch selector empty node → (node_2_a or node_2_b) → node_3

Related improvements:

• Branch handling now aligns with direct graph structure
• Unselected branch paths are disabled
• Selection remains driven via requirements/sidebar workflow

———

5) Manual approval skip flow now auto-syncs UI execution state

If a user manually approves in terminal/chat and the agent starts by calling update_node_status directly (without get_approval), the UI used to remain out of sync.

Now fixed: plan is auto-approved in UI when this pattern is detected, checklist hides, and execution state transitions correctly.

———

6) File attachments UX fixed in node sidebar

Previously, attachments relied on manual path entry input.

Now fixed:

• Uses file picker flow (single file selection)
• Selected file is saved server-side
• Absolute saved file path is returned and attached
• Better attachment selection UX in Node Detail sidebar

———

7) Prompt consistency rules added to both prompt directories

Updated all agent prompt files in:

• root prompts/
• packages/mcp-server/prompts/

Added mandatory Consistency section:

• ONE NODE EXECUTION AT A TIME
  Only one node may be executed at a time. Executing future nodes ahead of sequence is prohibited.
• CORRELATION TO OVERALL GOAL + CONTINUATION OF PREVIOUS NODES
  Node implementation must align with the end goal and continue prior established style/structure (not generic disconnected output).

———

🔧 Additional behavior update (branch message handling)

Branch-node messaging during update_node_status was refined to reduce agent confusion around already-made branch decisions by returning the explicit branch guidance message in description where
applicable.

———

⏳ Pending / Not Completed Yet

• Add settings for minimum amount of nodes per plan
  Status: Not yet implemented

———

Summary

This version primarily improves execution reliability, branch correctness, output observability, and prompt discipline, while also fixing practical UX issues like file attachment selection and manual-
approval execution sync.