The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and context window i...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Multiple
Build Time
Minutes
Fastest way to find out if claude-devtools belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/matt1398/claude-devtools ~/.claude/agents/claude-devtoolsRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/claude-devtoolsNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ claude-devtools/ ← installs here └─ settings.json
The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and context window in a visual UI. Free, open source.. An open-source agent for the AI coding ecosystem.