claude-devtools

Your Claude is coding blind. See everything it did.

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.

Zero configuration. No API keys. No wrappers. Works with every session you've ever run.

Installation

Homebrew (macOS)

brew install --cask claude-devtools

Direct Download

Key Features

Context Reconstruction

Per-turn token attribution across 7 categories — CLAUDE.md (global, project, directory), skills, @-mentioned files, tool I/O, thinking, team overhead, user text. See exactly what's in the context window at any point.

Compaction Visualization

See the moment your context hits the limit. Visualizes how context fills, compresses, and refills — so you know exactly what was lost.

Notification Triggers

System notifications for .env access, tool errors, high token usage, and custom regex patterns on any field.

Tool Call Inspector

Every tool call expanded with specialized viewers — syntax-highlighted Read calls, inline Edit diffs, Bash output, and full subagent trees.

Team & Subagent Trees

Isolated execution trees per agent with tool traces, token metrics, duration, and cost. Nested agents render recursively.

SSH Remote Sessions

Inspect sessions on any remote machine over SSH. Reads ~/.ssh/config, supports agent forwarding and key auth.

Command Palette & Multi-Pane Layout

Cmd+K for cross-session search. Open multiple sessions side-by-side with drag-and-drop tabs.

Not a Wrapper

claude-devtools does not wrap, modify, or interfere with Claude Code. It reads session logs that already exist on your machine. Works with sessions from the terminal, IDEs, or any tool that uses Claude Code.

Docker / Standalone Deployment

Run without Electron — in Docker, on a remote server, or anywhere Node.js runs.

docker compose up
# Open http://localhost:3456

Or manually:

docker build -t claude-devtools .
docker run -p 3456:3456 -v ~/.claude:/data/.claude:ro claude-devtools

The standalone server has zero outbound network calls. For maximum isolation: docker run --network none -p 3456:3456 -v ~/.claude:/data/.claude:ro claude-devtools. See SECURITY.md.

Development

git clone https://github.com/matt1398/claude-devtools.git
cd claude-devtools
pnpm install
pnpm dev

Contributing

See CONTRIBUTING.md for guidelines. Please read our Code of Conduct.

Security

IPC handlers validate all inputs with strict path containment checks. File reads are constrained to the project root and ~/.claude. See SECURITY.md.

License

MIT