Because nodes carry fields, files and per-step instructions, the review is not just yes or no — you can pick a branch, paste in an API key and add a note before a single line is written. Note that the gate is the agent's own blocking call rather than anything standing between it and your files: pause and re-run only take effect if the agent calls check_pause and check_rerun, and get_approval itself warns that a review can take 15–30 minutes, so whatever drives it has to be willing to wait.
An approval step between a coding agent and your codebase. The agent submits its plan as XML, a local UI renders it as a flowchart you can click through, and the agent blocks on get_approval until you accept it.
- Plans submitted whole with submit_plan, or amended in place — request_plan_update takes insert, delete and replace operations against a plan already on the canvas
- get_approval blocks until you accept or cancel, and hands back the field values you filled in and the branches you chose
- Per-node progress with update_node_status — pending, active, completed, failed or skipped, plus the output that node produced
- check_pause before each node and check_rerun after the plan finishes, so a pause or a re-run request reaches the running agent
- get_resume_info returns where a paused or failed plan stopped: the current node, which nodes are done, pending or failed, and the field values and branches already chosen
- Node details read and rewritten with get_node_info and update_node_detail, or many at once with update_nodes_detail — title, description, complexity, expected output, risks
- get_usage_instructions returns plan-format instructions tailored to the agent you name: claude-code, cline, cursor, sixth or gh_copilot
- Every call takes workspace_path, so several projects can be open against one UI at the same time
- Plans auto-save to ~/.overture/history.json and reload with their field values, branch selections and attachments intact
No account and no key. It starts as npx overture-mcp, or install it once with npm install -g overture-mcp. The UI opens on http://localhost:3031 and the WebSocket on 3030; OVERTURE_HTTP_PORT, OVERTURE_WS_PORT and OVERTURE_AUTO_OPEN change those. If the WebSocket port is already taken, Overture joins the existing server as a relay client rather than failing, which is how several agent instances share one UI. MIT.
One command — npx overture-mcp