[01]
Real cost & cache accounting
Sessions record token counts, not cost. cc-analyzer derives it from a per-model table, pricing input, output, and cache read/write separately — where most spend hides.
// read-only · local · single binary
Point it at the JSONL transcripts already sitting in ~/.claude and it reconstructs the ledger your Claude Code sessions never wrote down — cost, tokens, cache accounting, tools, skills, models, and a per-turn breakdown.
$ curl -fL …/releases/latest/download/cc-analyzer-darwin-arm64
$ cc-analyzer stats
scanning ~/.claude/projects … 342 sessions
────────────────────────────────────────────
total spend $1,284.57
turns 8,912
tokens 213M in · 52B cache
top model claude-opus-4 · 61%
────────────────────────────────────────────
✓ index up to date · read-only
$ ▋Sessions record token counts, not cost. cc-analyzer derives it from a per-model table, pricing input, output, and cache read/write separately — where most spend hides.
An amber-phosphor Ink TUI: a persistent nav rail and two-pane master-detail where the list drives a live preview, plus a full-screen session view with turns → steps, transcript, and summary.
cc-analyzer serve launches a Hono API and an embedded React dashboard: portfolio overview, project drill-down, and a windowed transcript reader.
A disposable local index that re-parses only changed sessions (by size + mtime), then powers portfolio-wide analytics — spend by month, project, and model.
Ships as one self-contained executable — CLI, TUI, API, and web UI baked in — cross-compiled for macOS, Linux, and Windows.
Never writes to ~/.claude. Its own state (pricing cache, index) lives under ~/.config/cc-analyzer. Your session data stays on your machine.
// quick start
Every release ships a self-contained binary for macOS, Linux, and Windows — or run it from source with bun. The index is a disposable local cache; delete and rebuild it any time.
# 1 · install — one line; detects your platform, grabs the latest binary
curl -fsSL https://cc-analyzer.brnby.com/install.sh | sh
# (Windows PowerShell one-liner in the install guide ▸)
# 2 · build the index from ~/.claude, then read the totals
cc-analyzer index
cc-analyzer stats
total spend $1,284.57 · 342 sessions · 8,912 turns
# 3 · dig in — one session, the TUI, or the local web app
cc-analyzer analyze <session-id> --json
cc-analyzer # interactive terminal UI
cc-analyzer serve # http://localhost:4317
✓ read-only · never writes to ~/.claude · your data stays on your machine