HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
SixHq
Overture
TypeScript2026–2026
SixHq / Overture

Overture

Overture is an open-source, locally running web interface delivered as an MCP (Model Context Protocol) server that visually maps out the execution plan of any AI coding agent as an interactive flowchart/graph before the agent begins writing code.

2Distinct people
3Mentions
0Explicit recommenders
642GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Overture is an open-source, locally running web interface delivered as an MCP (Model Context Protocol) server that visually maps out the execution plan of any AI coding agent as an interactive flowchart/graph before the agent begins writing code.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2026-02-22 09:44:17 UTC to 2026-03-09 13:30:58 UTC.

012026-02-22 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 222026-02-23 00:00:00 UTC to 2026-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 00:00:00 UTC to 2026-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-25 00:00:00 UTC to 2026-02-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 00:00:00 UTC to 2026-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-27 00:00:00 UTC to 2026-02-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-28 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 12026-03-02 00:00:00 UTC to 2026-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 00:00:00 UTC to 2026-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-04 00:00:00 UTC to 2026-03-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-05 00:00:00 UTC to 2026-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-06 00:00:00 UTC to 2026-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-07 00:00:00 UTC to 2026-03-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-08 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-10 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 9

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 222026-02-22 00:00:00 UTC2026-02-23 00:00:00 UTC110
Feb 232026-02-23 00:00:00 UTC2026-02-24 00:00:00 UTC000
Feb 242026-02-24 00:00:00 UTC2026-02-25 00:00:00 UTC000
Feb 252026-02-25 00:00:00 UTC2026-02-26 00:00:00 UTC000
Feb 262026-02-26 00:00:00 UTC2026-02-27 00:00:00 UTC000
Feb 272026-02-27 00:00:00 UTC2026-02-28 00:00:00 UTC110
Feb 282026-02-28 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 12026-03-01 00:00:00 UTC2026-03-02 00:00:00 UTC000
Mar 22026-03-02 00:00:00 UTC2026-03-03 00:00:00 UTC000
Mar 32026-03-03 00:00:00 UTC2026-03-04 00:00:00 UTC000
Mar 42026-03-04 00:00:00 UTC2026-03-05 00:00:00 UTC000
Mar 52026-03-05 00:00:00 UTC2026-03-06 00:00:00 UTC000
Mar 62026-03-06 00:00:00 UTC2026-03-07 00:00:00 UTC000
Mar 72026-03-07 00:00:00 UTC2026-03-08 00:00:00 UTC000
Mar 82026-03-08 00:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 92026-03-09 00:00:00 UTC2026-03-10 00:00:00 UTC110

What Hacker News says

1 sources

Show HN: Overture – Interactive plan viewer for AI coding agents (open source)

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
Read the rest
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.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.