Claude Devtools
The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and
Rating
Votes
0
score
Downloads
0
total
Price
Free
API key required
Works With
About
claude-devtools
Your Claude is coding blind. See everything it did.
Your browser does not support the video tag.
The Problem
Claude Code started hiding what it does.
Since v2.1.20, Claude Code replaced detailed output with opaque summaries. Read 3 files. Searched for 1 pattern. Edited 2 files. No file paths. No content. No line numbers. The community backlash was immediate.
But the problem goes deeper than collapsed file paths:
- Thinking steps — Claude's chain-of-thought reasoning is completely invisible in the terminal
- Tool call details — you see a one-line summary, not the actual input/output
- Subagent activity — agents spawn agents, but you only see the final result
- Context window — a three-segment progress bar with no breakdown of what's consuming your tokens
- Team coordination — teammate messages, task delegation, shutdown requests — all buried
The only workaround is --verbose, which dumps raw JSON, internal system prompts, and thousands of lines of noise. There is no middle ground.
The Solution
claude-devtools reads ~/.claude/ — the session logs already on your machine — and reconstructs everything.
| What the terminal hides | What claude-devtools shows |
|---|---|
Read 3 files | Exact file paths, syntax-highlighted content with line numbers |
Searched for 1 pattern | The regex pattern, every matching file, matched lines |
Edited 2 files | Inline diffs with added/removed highlighting |
| Three-segment context bar | Per-turn token attribution across 7 categories with compaction visualization |
| Collapsed subagent output | Full execution trees per agent with tool traces, tokens, duration, cost |
| Nothing about thinking | Extended thinking content, fully visible |
--verbose JSON dump | Structured, filterable, navigable interface — no noise |
Zero configuration. No API keys. No wrappers. Works with every session you've ever run.
Installation
Homebrew (macOS)
brew install --cask claude-devtoolsDirect Download
Don't lose this
Three weeks from now, you'll want Claude Devtools again. Will you remember where to find it?
Save it to your library and the next time you need Claude Devtools, it’s one tap away — from any AI app you use. Group it into a bench with the rest of the team for that kind of task and you can pull the whole stack at once.
⚡ Pro tip for geeks: add a-gnt 🤵🏻♂️ as a custom connector in Claude or a custom GPT in ChatGPT — one click and your library is right there in the chat. Or, if you’re in an editor, install the a-gnt MCP server and say “use my [bench name]” in Claude Code, Cursor, VS Code, or Windsurf.
a-gnt's Take
Our honest review
The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and. Best for anyone looking to make their AI assistant more capable in search & web. It's completely free and works across most major AI apps. This one just landed in the catalog — worth trying while it's fresh.
Tips for getting started
Tap "Get" above, pick your AI app, and follow the steps. Most installs take under 30 seconds.
Heads up: this needs an API key to work. You'll get one from the service's website (usually free). The setup guide tells you exactly where.
What's New
Imported from GitHub
Ratings & Reviews
0.0
out of 5
0 ratings
No reviews yet. Be the first to share your experience.