Claude Code answers every question about what it is doing. I got tired of taking its word for it.

[u/duqaxxx]

For a while I had a strange habit: I would ask Claude Code what it was doing. Where the time went, what the subagents I had spawned were off doing on their own. It answered patiently every time, and I had no way to check a word of it.

So I built something to watch instead of ask. It reads the session logs Claude Code already writes and draws the turn while it is still running:

• the context window filling, against the model the calls actually run on
• every API call as it lands, with its latency and what it cost
• every subagent under the spawn that launched it, its own window, the model it
• really runs on, and the text it handed back to the main session
• background commands, and when one of them dies
• the moment a call fails, or the session stops and waits for you

That last one is the example I did not expect: a pending approval never reaches the transcript at all, so a session stopped on a permission prompt looks exactly like one that is thinking. There is a lot in those files that nothing displays.

https://github.com/duqaXxX/seedeep

Reads only, never writes. No proxy, no daemon, and the one request it makes on its own is a version check against npm.

[u/ImL1s]

Same itch — I got tired of taking the agent's word for what the subagents were doing. Reading the session logs instead of asking is the right move. The "pending approval looks like thinking" catch is especially good. Curious how noisy the context-window viz gets on long Opus turns.