I built this because I got tired of the Claude Code CLI hiding details from me.
Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts.
I wanted a middle ground: *Full observability without the noise.*
`claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time.
*Unlike wrappers, it solves the visibility gap in your native terminal workflow:* 1. *Real Diffs:* It shows inline diffs (red/green) the moment files are edited, instead of just a checkmark. 2. *Context Forensics:* It breaks down token usage by File vs Tool Output vs Thinking (so you know exactly why your context window is full). 3. *Agent Trees:* It visualizes sub-agent execution paths which are usually interleaved and confusing in the CLI.
It’s 100% local, and works with the logs already on your machine. No API keys required.
Repo: https://github.com/matt1398/claude-devtools (Screenshots and diff viewer demo are in the README)
Opencode is great as a full replacement. Works out of the box.
Pi code agent[1] is even better, if you spend some time in it, you can customize is to your liking. It's a vi and Emacs combined for agents.
[1] https://pi.dev
Claude Code is not developer friendly.
But regarding khoury's original point about the actual "gas in the tank" (billing/account balance)—no, my tool doesn't show that either.
Since `claude-devtools` strictly parses your local `~/.claude/` logs and makes zero network calls, it doesn't have access to your Anthropic account to pull your actual dollar balance.
What it does provide is high-resolution context usage. Instead of just a total session count, it breaks down tokens per-turn (e.g., how many tokens were eaten by reading a specific file vs. the tool output). It helps you manage your context window locally, but for billing, you're unfortunately still stuck checking the web dashboard.
Deleted Comment
I think there are quite a few bugs lingering in those agent-cli's and observability, would help a lot with reporting. Taking yours for a spin this evening, thank you!
Thanks for giving it a spin tonight! Let me know if you run into any issues.
Also, this isn't a wrapper—it’s a passive viewer. I built it specifically to keep the native terminal workflow intact.
It’s especially useful when you're running multiple parallel sessions. Have you ever tried digging through raw JSON logs to retroactively debug passed sessions at once, since the session is already shut down? It’s nearly impossible without a proper UI. This tool is for those "post-mortem" moments, not just for watching a single stream.
"claude-trace" Record all your interactions with Claude Code as you develop your projects. See everything Claude hides: system prompts, tool outputs, and raw API data in an intuitive web interface.
https://github.com/badlogic/lemmy/tree/main/apps/claude-trac...