Local dashboard tracks Claude Code usage with token costs, tool calls, and session analytics
What it does
A developer created a local dashboard that provides visibility into Claude Code usage by reading directly from the ~/.claude/ directory. The tool visualizes session data without sending information to external services.
Key features
- Token usage and estimated cost per session and per project
- 30-day cost chart with daily breakdown
- Tool call breakdown (Read, Write, Bash, Grep, etc.)
- Most-edited files across all sessions
- Hour-of-day activity heatmap
- Full conversation viewer - click any prompt to see every tool call and response
- Cache hit rate (shows how efficiently context is being reused)
- Active streak tracking and session history with search functionality
How it works
The dashboard uses an Express API to read the JSONL session files that Claude Code writes locally. The frontend is built with React, and all data processing happens on your machine. The developer mentions they built this because they "had no visibility into what it was actually doing, which sessions cost the most, which tools it calls most often" when using Claude Code heavily.
The tool is available on GitHub at https://github.com/rohitsasi720/claude-code-tracker.
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude AI's UltraThink feature returns with practical usage guidance
Claude AI has reinstated the UltraThink feature after user feedback. Medium effort is now the default for Opus 4.6 (Max/Team), with High effort available permanently via /model, and UltraThink as a one-turn override to high effort.
Claude Code + MCP generates test suites from source code
Claude Code analyzes source code to generate hierarchical test suites covering modules, features, scenarios, happy paths, edge cases, and error handling, then pushes them to test management systems via MCP.
Applying Claude Code's Architecture to Local 9B Models: Key Findings and Optimizations
A developer extracted architectural patterns from Claude Code's leaked source code and applied 10 optimizations to qwen3.5:9b running locally on an RTX 5070 Ti. The key discovery was that qwen3.5:9b has native structured tool_calls, and the biggest limitation for 9B models is self-discipline in knowing when to stop exploring and start producing output.
NervMap: Single Command Server Service Discovery and Diagnostics Tool
NervMap is a Linux tool that discovers Docker containers, systemd services, and bare processes in under 1 second, maps dependencies between them, and diagnoses issues with severity analysis and fix suggestions.