|
As a daily Claude Code and Cursor user, something that kept frustrating me
is that plans are just a flat list of steps in the terminal and chat screen.
I can't monitor what's happening at each step while it runs — I just wait
for the whole thing to finish and hope it worked. If I want to restructure
the plan, I'm copy-pasting text around in a chat box. I can't attach
specific instructions or files to step 4 without it leaking into step 7.
I can't tell one step to use the Figma MCP and another to use Supabase. So I built Overture. It's an open-source MCP server that takes the agent's
plan and turns it into an interactive node graph in your browser before any
code gets written. I can now click into any step and attach exactly what it needs — files,
docs, API keys, an MCP server, special instructions — scoped to just that
step. I can drag to reorder, delete steps, add new ones. I can see which
steps depend on which. When the plan has a branch point (like Stripe
Checkout vs Stripe Elements), I can pick one or run both in parallel and
choose the winner. During execution, each node updates individually —
green when done, red with logs when failed, and I can inspect the output
of any step without waiting for the full run to finish. Works with Claude Code, Cursor, Cline, Codex — anything that supports
MCP. Plans are structured XML under the hood, and agents can declare input
fields per step ("this step needs a Stripe API key") so I fill everything
in upfront instead of getting interrupted mid-execution. npx overture to try it. Everything runs locally. Still early — contributions very welcome. Graph rendering, layout
algorithms, and getting agents to consistently generate structured plans
are all areas that need work. |