I built a local dashboard to inspect Claude Code sessions, tokens, and costs

I’ve been using Claude Code heavily over the last few weeks and started wondering where my tokens were actually going.

Claude stores everything locally in ~/.claude/, which is great, but the data mostly sits in JSON logs. If you want to understand session usage, token costs, tool calls, or activity patterns, you basically end up digging through raw files.

So I built a small tool called cc-lens.

I built a local dashboard to inspect Claude Code sessions, tokens, and costs
It’s a local-first dashboard that reads your Claude Code session files and turns them into something you can actually explore.

It runs entirely on your machine. It doesn't have any cloud sync, sign-ups, or telemetry.

Some things it shows:

• Usage overview: sessions, messages, tokens, estimated cost
• Per-project breakdown: see which repos are burning the most tokens
• Full session replay: inspect conversations turn-by-turn with token counts and tool calls
• Cost & cache analytics: stacked charts by model and cache usage
• Activity heatmap: GitHub-style view of when you’re using Claude the most
• Memory & plan explorer: browse/edit Claude memory files and saved plans
• Export/import: move dashboards across machines

You can run it instantly with:

npx cc-lens
(or clone the repo if you prefer).

Here's the Github Repo, if you want to try it out!