skills.rest
reason-machines
reason-machinesOFFICIAL
Explore all skills by this author →
Website𝕏@reasonmachinesGitHub

claude-devtools-inspector

Inspect Claude Code session logs, tool calls, token usage, and subagent traces.

4|Updated May 16, 2026
Search Tags:#debugging#claude code#observability#devtools#token usage#session logs#jsonl
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill claude-devtools-inspector-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-devtools-inspector
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/claude-devtools-inspector
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill claude-devtools-inspector-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code hides tool calls, token usage, thinking steps, and subagent activity from the terminal, making it hard to debug sessions, understand context compaction, or audit what the agent actually did. ## Core Features & Use Cases - Session Inspection: Reconstruct full transcripts from JSONL logs in ~/.claude/ with syntax-highlighted messages and exact tool inputs/outputs. - Token & Context Analysis: Per-turn token attribution across 7 categories plus visualization of context compaction events and dropped segments. - Subagent & Memory Viewing: Trace nested subagent execution trees with cost metrics and browse project memory layers. - Use Case: When Claude appears to forget earlier instructions, open the session in claude-devtools, check the Context tab for compaction events, and see exactly which segments were dropped at which turn. ## Quick Start Install claude-devtools via Homebrew or Docker, then open the UI to inspect the current Claude Code session's tool calls and token usage.

Frequently Asked Questions about claude-devtools-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect Claude Code session logs?▼

Install claude-devtools via Homebrew (brew install --cask claude-devtools) or run it in Docker with ~/.claude mounted read-only. Sessions appear automatically in the sidebar with full transcripts, tool calls, and thinking steps.

How to check Claude Code token usage per turn?▼

Open the session in claude-devtools and view the token attribution breakdown across 7 categories including CLAUDE.md, skills, tool I/O, and thinking. You can also query the JSONL logs directly with jq filtering on tokens.input.

Does claude-devtools work with existing Claude Code sessions?▼

Yes, it reads existing JSONL logs from ~/.claude/sessions/ with no wrapper, API keys, or configuration required. It also supports inspecting sessions on remote machines over SSH using your ~/.ssh/config.

Why is my Claude Code session not appearing in claude-devtools?▼

Claude Code only writes logs for sessions started with the --session flag or project-level sessions. Verify ~/.claude/sessions/ exists with proper permissions (755 directory, 644 files) and force a UI refresh.

Can claude-devtools modify or delete my session data?▼

No, claude-devtools is strictly read-only and never modifies session logs. The standalone server makes zero outbound network calls, and you can run Docker with --network none for full isolation.

Related Skills

Explore More Software Engineering Skills→
searlscosearlsco
199

session-log

Inspect Claude Code session logs for reviewer verdicts and session states.

Official
Intermediate
prince-khannaprince-khanna
1

analyze-team-session

Analyze agent team session markdown exports and generate a structured evaluation report.

Community
Advanced
genesis-agentsgenesis-agents
2

Steward

Monitor budget usage and emit tiered alerts enforcing token and cost thresholds.

Community
Intermediate
darblexdarblex

Claude Code Control

Control Claude Code sessions via AppleScript keystrokes and capture screenshots on macOS.

Community
Advanced