Claude DevTools: A Log Reader for Enhanced Claude Code Visibility

Claude DevTools is a utility that addresses common frustrations with Claude Code's terminal output by parsing the existing log files in your ~/.claude/ folder. It provides detailed visibility into sessions without modifying how Claude Code itself operates.
Key Features
- Full visibility into operations: Shows every file read, every edit with inline diffs, and every bash command executed, replacing vague summaries like "Read 3 files" with specific, syntax-highlighted details.
- Token breakdown per turn: Splits context usage across seven categories: CLAUDE.md files, tool call inputs/outputs, thinking tokens, skill activations, user text, and others, helping identify what consumes the context window.
- Context window visualization: Displays how context fills over a session, when compaction occurs, and what gets dropped, clarifying why Claude might forget information mid-conversation.
- Full subagent visibility: When Claude uses the Task tool to spin up sub-agents, it renders each agent's full execution tree—including prompts, tool calls, token usage, cost, and duration. If agents spawn more agents, it displays the entire nested tree. Team features like TeamCreate and SendMessage show each teammate as a color-coded card.
- Thinking output: Allows reading extended thinking blocks alongside tool traces to understand the reasoning behind Claude's decisions.
- Custom notifications: Supports alerts for events such as
.envfile access, tool execution errors, or token usage spikes past a threshold, with regex triggers for sensitive file paths. - Works with all sessions: Reads raw log files, capturing sessions from the terminal, VS Code, and other tools without data loss.
- Multiple deployment options: Available as an Electron app, Docker container, or standalone Node server accessible via browser, useful for remote setups or avoiding Electron.
- Zero setup: Requires no API keys or config files—just install and open.
- Open-source and local: The tool is open-source, runs locally, and is read-only, not interfering with Claude Code's operation.
The tool is designed for heavy Claude Code users who need more transparency than the default terminal output provides. It runs independently, leveraging existing logs to deliver detailed insights into session activity.
📖 Read the full source: r/ClaudeAI
👀 See Also

OpenClaw Janitor Skill for Automated System Management and Security Hardening
A developer created a skill that uses Claude Code to SSH into OpenClaw machines and harden configurations, including sandboxing, OS hygiene, and channel security, while maintaining a project folder with audit instructions in CLAUDE.md.

Why Your Claude Code UI Output Drifts and How a Structured Spec Fixes It
A developer explains that inconsistent UI output from Claude Code isn't a prompt problem — it's a format problem. Providing exact hex codes, font weights, spacing, screen states, and transitions eliminates drift. They also open-sourced an MCP server that converts screen recordings into structured specs.

OpenClaw Benchmark Shows Qwen3.5:27B Outperforms Other Local LLMs for Agent Tasks
A benchmark of 7 local LLMs on 22 real agent tasks using OpenClaw found qwen3.5:27b-q4_K_M scored 59.4%, while the runner-up qwen3.5:35b scored only 23.2%. Most models couldn't find basic tools like email functions.

NotebookLM MCP Structured: Free Server Connects Claude to NotebookLM with Automatic Prompt Structuring
A free MCP server called NotebookLM MCP Structured connects Claude Desktop to NotebookLM notebooks with automatic prompt structuring. The server restructures queries based on type (comparison, list, analysis, explanation, or extraction) and adds completeness checks and fidelity constraints.