Seedeep

seedeep

*See deep into what Claude Code is doing.*

Claude Code writes a session log to disk as it runs. seedeep tails that log and
rebuilds the turn while it is still happening: the context window filling, every API
call with its latency and token split, every tool call and its result, and each
subagent folded under the spawn that launched it. The same view is there afterwards
to walk through.

Read-only. No proxy, no daemon, no session content leaves the machine.

*One turn, from 3% to 26% of the window: six subagents on three different models,
2.9M tokens billed, 2.5M of them the same context read again.*

Why you'd run it

Eight things a Claude Code session does not report, and what seedeep shows instead.

- A failed API call ends the turn silently. An expired login, a session limit, an
  overloaded server: the turn stops, the terminal keeps looking normal, and the
  transcript's last line is the error itself. seedeep turns the tab red, files the
  session under *Broken*, and turns the menu-bar icon red above every other signal.
- An approval dialog reaches no log at all, so a session stopped on a permission
  prompt looks identical to one that is thinking. seedeep reads Claude Code's own
  live state, turns the tab amber the moment it stops, and names what is waiting to
  be approved.
- Subagent spend is invisible from the terminal. The live tree shows each subagent as
  it launches: its own context filling, the model it actually runs on, and the
  verbatim output it handed back to the main session.
- The window size depends on the model. The bar follows the model your calls really
  run on, so /model mid-session moves it, and a Haiku subagent is measured against
  200k inside a session running on 1M.
- Most of what you spend is context you already sent. Measured…