
claude-devtools

Open-source tool to view hidden details from Claude Code sessions: thinking steps, tool calls, context window, subagent trees. No API keys needed. Works with logs already on your machine.
Editor's Verdict
Key Takeaways
- Context Reconstruction
- Copy & Paste Without Terminal Pain
- Tool Call Inspector
- Project Memory
In-Depth Review: What is claude-devtools?
Claude DevTools restores the visibility that Claude Code's terminal output hides. Since version 2.1.20, detailed session logs were replaced with opaque summaries. This tool reads the raw session files from ~/.claude/ on your machine and presents them in a clean, interactive interface. It reveals thinking steps, exact tool inputs and outputs, subagent activity trees, context window breakdowns, file paths with diffs, and team coordination details. Features include a tool call inspector with syntax highlighting, project memory viewer, notification triggers, SSH remote session inspection, cross-session command palette search, and multi-pane layout for comparing sessions. It's open source under MIT, requires no login or API keys, and makes zero outbound calls.
Core Features
Context Reconstruction
Per-turn token attribution across 7 categories including CLAUDE.md, skill activations, @-mentioned files, tool I/O, thinking, team overhead, and user text. Visualizes context fill, compression, and refill over time.
Copy & Paste Without Terminal Pain
Renders every message, tool call, and output as real selectable text. One-click copy for code blocks, file paths, or entire responses. Works consistently on macOS, Linux, and Windows.
Tool Call Inspector
Syntax-highlighted Read calls, inline Edit diffs, Bash output, and full subagent execution trees. Expands every collapsed summary like 'Read 3 files' into detailed views.
Project Memory
Opens per-project Claude memory from ~/.claude/projects/<project>/memory/ in a dedicated pane with layer list, full markdown rendering, search, and launcher for external editors.
Team & Subagent Trees
Isolated execution trees per agent showing tool traces, token metrics, duration, and cost. Nested agents render as recursive trees for clear visibility.
Notification Triggers
System notifications for .env file access, tool errors, and high token usage. Supports regex triggers on sensitive paths, token thresholds, and color filtering.
SSH Remote Sessions
Inspect sessions on remote machines over SSH using ~/.ssh/config, agent forwarding, and key auth. Instantly switch between local and remote views.
Command Palette
Cmd+K opens cross-session search with context snippets and highlighted keywords. Navigate directly to any message.
Multi-Pane Layout
Open multiple sessions side-by-side with drag-and-drop tabs between panes, split views, and parallel session comparison.
Pricing
Open Source Free Edition
- All features included
- No login required
- No API keys needed
- Zero outbound calls
- Open source MIT license
Pros and Cons
Pros
- Full Visibility into Claude SessionsRestores detailed visibility that Claude Code removed, showing thinking steps, tool I/O, subagent activity, and more.
- Free and Open SourceMIT licensed with no cost, login, or API keys. Zero outbound calls ensure privacy.
- Works Offline with Existing LogsReads local session logs from ~/.claude/ without modifying Claude Code or requiring internet.
- Cross-Platform SupportAvailable on macOS, Windows, and Linux via native installers and Docker.
- Developer-Friendly FeaturesIncludes command palette, multi-pane layout, SSH remote sessions, and notification triggers for efficient debugging.
Cons
- Only Works with Claude Code LogsRequires sessions recorded by Claude Code; not applicable to other AI tools.
- Limited to Local Logs by DefaultWithout SSH configuration, only inspects sessions on the local machine.
Use Cases & Recommended Professions
Software Developer→ View Toolkit
Uses Claude Code for coding assistance and needs to review detailed session logs to understand AI decisions and debug outputs.
AI/ML Engineer→ View Toolkit
Relies on Claude Code for model interaction and requires full transparency into token usage, reasoning steps, and tool calls to optimize prompts.
DevOps Engineer→ View Toolkit
Manages automated workflows with Claude Code and needs to inspect subagent activities, SSH sessions, and error triggers for reliability.
Technical Writer→ View Toolkit
Documents Claude Code interactions and needs clear copy-paste functionality and context reconstruction for accurate reporting.
QA Engineer→ View Toolkit
Tests Claude Code behavior and requires detailed tool call I/O and notification triggers to identify anomalies.
Engineering Manager→ View Toolkit
Oversees teams using Claude Code and needs visibility into team coordination, memory usage, and subagent costs for resource planning.
Frequently Asked Questions
Alternative AI Tools
View Detailed Comparison →ℹ️ Curation Disclosure: The overview and features of claude-devtools were synthesized using AI and fact-checked by our curation team to ensure accuracy.










