u/Express-Phase1532

My coding agent kept doing 20 minutes of work I couldn't inspect afterward. The transcript exists (Claude Code and Codex CLI write everything to disk), but nobody reads 4,000 lines of JSON.

So I built rungraph, open source and free (MIT). npx rungraph turns every session on your machine into a clickable graph: your prompts run down the spine, subagents get their own lanes, and it flags stuff like retry loops and errors nothing came back to fix. If a session is still running, the graph fills in as the agent works. And new in 0.4.0, you can resume any local session from the dashboard: copy the exact resume command, or one click opens it in a terminal on macOS.

Nothing leaves your machine.

Live demo in the browser, nothing to install: https://fayzan123.github.io/rungraph 

Repo: https://github.com/fayzan123/rungraph

Feedback welcome, especially if it breaks on your transcripts.

Disclosure up front: I built this. It's free, MIT, and shipped (npm: rungraph).

Claude Code and Codex CLI write full session transcripts to disk, and rungraph reconstructs them into interactive run graphs. The MCP server is the part this sub might find interesting: npx rungraph mcp --install gives your agent tools over its own history. list_runs, get_graph, find_nodes, get_detail, focus_nodes, get_current_view, open_visualization.

The design problem was context size. A real 176-node run is about 20k tokens as a full graph, 13.5k in the compact projection, and 1.1k through find_nodes. Narrowing beats projecting, so the tool descriptions steer agents to find_nodes first, then get_detail for one node's actual error text.

The fun tool is focus_nodes. You ask Claude in your own terminal "why did the Edit on token.js keep failing", it answers there, and the dashboard you have open lights up the exact nodes the answer is about, then returns a deep link that restores the same highlight against that dashboard (or a bundle the recipient has open). Honest limitation: with no dashboard watching, the call still succeeds and just reports that the highlight was skipped. The read tools parse straight from disk, so they work with no server running at all.

Implementation note for the protocol nerds: the JSON-RPC transport is hand-rolled over stdio because the package has zero runtime dependencies, which keeps the npx install tiny. If more than one dashboard is live (yours, plus a bundle someone sent you), list_runs merges them and every other tool routes by run id.

Live Demo: https://fayzan123.github.io/rungraph/

Repo: https://github.com/fayzan123/rungraph

If you wire it into a client other than Claude Code, I'd like to hear whether the tool descriptions hold up