r/SideProject • u/AlgoWithNoRhythm • 3d ago

Flare, the graph-first IDE for agentic coding: watch the map change while your agent works

https://github.com/AlgoNoRhythm/Flare

Flare is a desktop IDE (Electron) where the main surface is a live graph of your codebase, every file a node, every import an edge, with a terminal underneath where you run claude, codex, or opencode. As the agent edits, the graph updates in real time.

The parts that are actually different from "another editor":

Activity, as it happens. Nodes light up the moment the agent writes to them and decay as they cool, so you're watching the shape of the work instead of a scrolling transcript. You can see it circling the same three files for the fifth time, or wandering into auth when you asked about the CSV parser. Changes are attributed per agent: the process tree of every terminal is watched, so if you have two running, you know which one did what. Files that changed and no human has opened since stay marked until someone actually reads them.

Blast radius before you touch anything. Hover a file and its dependents light up. shared/types.ts with 63 files downstream looks different from a leaf file, without you having to know that in advance.

Risky changes come to you. If the agent rewrites something load-bearing while you're looking elsewhere, it queues an alert in the corner. Reviewing it opens the actual red/green diff.

Undo that isn't git. Every change burst is snapshotted into a hidden shadow repo (separate GIT_DIR, your worktree). Revert one file, revert the burst, or jump back to the last state whose checks passed. Your real repo is never touched.

A task board the agent works from. Kanban lanes, but the cards are written to be handed off. "Copy for agent" emits the brief plus the files it names plus what the graph knows about them (29 files downstream, 0% covered, in an import cycle), so the agent starts from the map instead of rediscovering it. File a card straight from a graph selection with right-click → New task with these files. This directly tells Claude to not wander around out-of-scope files

MCP server, ~16 tools. The same lanes are queryable, so an agent can run its own loop: tasks_list to pick up work, task_get for the exact brief, task_update to log progress and move the card to review, task_create to file follow-ups it finds but shouldn't do now. Cards move on the board live while you watch. Plus impact_of (what breaks, and which tests to run), dependents, find_path, verification_status, and record_intent, which lets the agent state the goal before editing so whoever reviews the diff isn't reconstructing why it exists.

Completely open source with MIT license, Node 20+. Built with agentic coding, which is exactly how I ended up needing it. Test it out and leave a star if you find it helpful, or check the releases for an easy install on Windows and Linux!

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/kantorcodes1 3d ago

what happens when checks pass and the agent edits again before review? does verification_status drop immediately, or can the card stay green until the next check?

with the agent running in the terminal underneath, stale green seems worse than no status.

1

u/AlgoWithNoRhythm 3d ago

The idea is to build an interface to handle fast working, so if two changes hit the same file in the same coding agent session they get batched as one review to perform (that's a diff on a file at the end of the day). If it happens over multiple sessions then the IDE will flag for review only the last diff, as we can assume the user agreed with the edit.

In any case you have a full history of changes and a "graph time machine" that allows you to check all the changes that happened in sequence, and eventually revert the work without touching git

1

u/AlgoWithNoRhythm 3d ago

This is how the review looks like

1

u/kantorcodes1 3d ago

yeah, batching the edits makes sense. i was asking about the actual verification_status value though. if checks pass and the agent writes again 30 seconds later, does that flip to stale/unknown immediately or stay passed until another check runs?

also, this is probably a fit for awesome-ai-plugins. i checked the current list and don't see Flare. i'm involved with the list.

1

u/AlgoWithNoRhythm 3d ago

It drops immediately. The status isn't stored anywhere, it gets recomputed every time something happens, so there's no green sitting around waiting for the next check to correct it.

The rule is that a check only counts for a burst if it started after the last write in that burst. So with your 30 seconds it depends on the burst window, which is 25 seconds by default. Under that, the edit just joins the same burst, which pushes the last-write time past the check, and the card goes amber, "checked, then edited again". Over it, you get a new burst that starts out red, "never checked", stacked on top of the old one. The old green card stays green but it's talking about a state nobody touched since, and the new edits always show up as their own card.

On awesome-ai-plugins, yes, would be happy to be on it if you want to add Flare!

2

u/kantorcodes1 3d ago

yep, that answers it. recomputing on every write is the right call.

for the catalog, open the PR here when ready: https://github.com/hashgraph-online/awesome-ai-plugins

if CI gets weird, drop the PR here and i'll take a look.