So I’ve been using Claude Code a lot lately and ran into the usual annoyances. The summarized outputs where it just says “Read 3 files” or “Edited 2 files” with no details. The scrollback issues. Context getting wiped when compaction kicks in. The terminal history being cleared to manage RAM. You know the deal. Then I found claude-devtools and it pretty much solved all of that for me. I still use Claude from the terminal as my main workflow, it’s not a wrapper or anything that changes how Claude Code works. It just reads the log files that already exist in your ~/.claude/ folder and turns them into something you can actually make sense of. Here’s what makes it worth it: Full visibility into what actually happened. Every file that was read, every edit with a proper inline diff, every bash command that ran. No more “Read 3 files” with zero context on which files or what was in them. Everything is syntax highlighted. Token breakdown per turn. It splits your context usage across 7 categories like CLAUDE.md files, tool call inputs/outputs, thinking tokens, skill activations, user text and more. You can finally see exactly what’s eating your context window instead of staring at a vague progress bar. Context window visualization. You can literally watch how your context fills up over the session, when compaction happens, and what gets dropped. If you’ve ever been confused about why Claude forgot something mid conversation, this clears it up fast. Full subagent visibility. This is my favorite part. When Claude spins up sub-agents with the Task tool, you can see each one’s full execution tree. Their prompts, tool calls, token usage, cost, duration. If agents spawn more agents, it renders the whole thing as a nested tree. Same goes for the team features with TeamCreate and SendMessage, each teammate shows up as a color coded card. Thinking output. You can read the extended thinking blocks alongside the tool traces, so you can actually understand why Claude made certain decisions instead of just seeing the end result. Custom notifications. You can set up alerts for stuff like when a .env file gets accessed, when tool execution errors happen, or when token usage spikes past a threshold. You can even add regex triggers for sensitive file paths. Works with every session you’ve ever run. It reads from the raw log files so it picks up sessions from the terminal, VS Code, other tools, wherever. Nothing is lost. Runs anywhere. Electron app, Docker container, or standalone Node server you can hit from the browser. Nice if you’re on a remote box or don’t want Electron. Zero setup. No API keys, no config files. Just install and open. The whole thing is open source and runs locally. It doesn’t touch Claude Code at all, purely read only on your existing session logs. If you’ve been frustrated with the lack of transparency in Claude Code’s terminal output, seriously check this out. It’s one of those tools where once you start using it you wonder how you managed without it. (I’m not the creator btw, just a user who thinks way more people should know about this thing) submitted by /u/Intelligent-Ant-1122
Originally posted by u/Intelligent-Ant-1122 on r/ClaudeCode