A web UI for ccusage — the Claude Code usage analyzer. See your Claude costs by day, month, session, and 5-hour billing block with interactive charts and per-model breakdowns, instead of re-running terminal commands.
Give it a try, contributions and feedback are welcome
Top comments (2)
Nice. The 5-hour block view is the part that makes this useful vs just checking totals after the fact. I’d also love a small “sessions that spiked” list so you can trace a bad run back to the prompt or repo state that caused it.
Nice - a web dashboard on top of the ccusage data is a genuinely useful upgrade over squinting at a CLI table, because cost data is one of those things people only act on when it's visual and glanceable. The fact that this category exists at all (multiple tools just to track Claude Code spend) is itself the tell: token cost has become a real budget line, not a rounding error.
The natural next step once you can SEE where the tokens go is closing the loop - turning observation into action. Visibility shows you "this kind of task is eating 60% of my spend"; the payoff is then routing those tasks to a cheaper model or trimming the context that's bloating them. Measure, then route. That observe-then-act loop is the core of how I keep Moonshift (a multi-agent pipeline that ships a prompt to a deployed SaaS) at ~$3 flat - the dashboard is step one, the routing is step two. Cool tool, the dev community clearly needs this. Are you thinking of adding any actionable insights on top (like "this session would've been X% cheaper on a smaller model"), or keeping it pure tracking? The insight layer is where a tracker becomes indispensable.