Most agentic coding tools hand you a chat log. Flare hands you the map. Every file is a node, every import an edge, with a real terminal underneath where you run claude, codex or opencode. The graph updates live as the agent edits, attributes every write to whoever made it, and pulls you in when it rewrites something the rest of the app imports. Change bursts snapshot to local history you can diff and revert. Agents take work from a board over MCP. Your machine. No account. MIT licensed.
Hey Product Hunt 👋
I built Flare because I kept losing track of what my agents were doing.
You hand Claude Code or Codex a task, come back twenty minutes later, and
there are thirty changed files and a chat transcript. The transcript tells
you what the agent said. It doesn't tell you that one of those files is
imported by nine others, or that the one change nothing tests is the one
holding the app together.
So Flare reads the repo instead of the conversation. Files become nodes,
imports become edges, and the map updates as the agent writes. Every change
is attributed so when two agents cross over the same
file you see it as a crossing on the map, not as a merge conflict tomorrow.
A few things I'm glad I got right:
• The terminal is a real terminal. Bring your own agent. Flare doesn't wrap
it, proxy it, or touch your keys.
• Every change burst is snapshotted locally, so you can diff and revert one
file or the whole tree without involving git. You also get notified by every risky change and have access to a "diff sub-graph" showing what changed in the last session.
• The task board is exposed over MCP, so the agent picks up work and asks its
questions there. You're both looking at the project rather than at each
other's messages.
• It all runs on your machine. No account, no telemetry, no cloud. MIT licensed.
I'd love to hear how you're keeping track of what your agents change right
now, and if you try it, what the graph tells you about your own repo that
you didn't already know.
Can multiple agents work on the same project at once while Flare shows their changes separately?
About Flare on Product Hunt
“The graph-first IDE and interactive map for agentic coding”
Flare launched on Product Hunt on August 25th, 2026 and earned 120 upvotes and 4 comments, placing #11 on the daily leaderboard. Most agentic coding tools hand you a chat log. Flare hands you the map. Every file is a node, every import an edge, with a real terminal underneath where you run claude, codex or opencode. The graph updates live as the agent edits, attributes every write to whoever made it, and pulls you in when it rewrites something the rest of the app imports. Change bursts snapshot to local history you can diff and revert. Agents take work from a board over MCP. Your machine. No account. MIT licensed.
Flare was featured in Open Source (68.8k followers), Developer Tools (518.5k followers) and Vibe coding (650 followers) on Product Hunt. Together, these topics include over 98.2k products, making this a competitive space to launch in.
Who hunted Flare?
Flare was hunted by AlgoMauro. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Flare stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
AlgoMauro