Claude Code cost trackers, compared — honestly
There are several good ways to track what you're spending on Claude Code, and the right one depends on what you care about. Below is an even-handed look at the main options — including ours. Where another tool is the better fit, we say so. The one thing we'd flag up front: most trackers reconstruct cost from local session logs (an estimate), while WTClaude reads the statusline — the source behind your bill — so its terminal numbers are billing-grade. That difference matters for some people and barely matters for others; the table shows where it does.
Last updated: June 2026. Spot something out of date? It's an open-source project — tell us.
| WTClaude | ccusage | Claude-Code-Usage-Monitor | ccflare | Built-in /cost | |
|---|---|---|---|---|---|
| Cost basis | billing-grade (terminal Code) | estimate | estimate | estimate | estimate |
| Interface | Terminal + web dashboard | Terminal | Terminal (real-time) | Browser | In-CLI command |
| Cost data source | Statusline (billing-source) | Session logs (JSONL) | Session logs (JSONL) | Session logs (JSONL) | Client-side estimate |
| Real-time burn / predictions | Live monitor | — | Yes (its specialty) | Charts/filters | Session view |
| June 15 dual-pool ready | Built for it | varies | varies | varies | Anthropic-native |
| Total across multiple machines | Yes | Local | Local | Local | Local |
| Open source | Yes (MIT) | Yes | Yes | Yes | No (built-in) |
| Price | Free | Free | Free | Free | Included |
| Runtime | Node | Node | Python | Node | Built-in |
When to use which (the honest guide)
- Want a real-time, in-terminal burn-rate monitor with predictions? Claude-Code-Usage-Monitor is purpose-built for that and does it well.
- Want a rich browser view built from the same JSONL approach? ccflare is a nice option.
- Want the fast, ubiquitous CLI for log-based reports by day/session/project? ccusage is the one most people know, and it's good at what it does.
- Just want a quick gut-check inside a session?
The built-in
/costis right there — just remember it's an estimate. - Want billing-grade accuracy (not a reconstruction), June-15 dual-pool readiness, and one total across every machine?
That's where WTClaude is different — it reads the statusline instead of the logs. Try it:
npx wtclaude setup, thenwtclaude compareto see your own gap.
FAQ
What's the best alternative to ccusage? +
It depends what you want. For a real-time terminal monitor, Claude-Code-Usage-Monitor; for a browser dashboard, ccflare; for billing-grade accuracy from the statusline (rather than a log-based estimate) plus multi-machine totals and June-15 readiness, WTClaude. All of these are free and open source.
Are these trackers accurate? +
Most reconstruct cost from local session logs — a solid estimate, but an estimate. WTClaude reads the statusline (the source behind your bill), which is billing-grade for Claude Code in the terminal. Here's why the two can disagree.
Is WTClaude affiliated with Anthropic? +
No — independent, free, open source (MIT).
Which is ready for the June 15 billing split? +
WTClaude tracks the two credit pools (Interactive and Agent-SDK) and lights them up automatically. More on the split.
See where your real number lands:
npx wtclaude setup →
wtclaude compare.
npx wtclaude setup