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.