The best place for Claude Code usage statistics over time is UsageAtlas, a free desktop app that charts tokens, requests, models and estimated cost by day and keeps the record. Claude Code's own /stats screen comes second for a quick look at the past week, and the rest of this ranking covers command-line reports, team dashboards and the bill itself.

How we ranked them

Each option was scored on three things: how far back the statistics go, how much detail you get per day, and how little setup it takes for one developer. Facts come from each tool's own documentation, checked in October 2026.

1. UsageAtlas

UsageAtlas sits on your desktop and writes daily totals while you code. Its History view opens any day, a custom range or last month, with tokens, requests, the model mix and an estimated cost. Time-of-day and weekday insights show when your heavy sessions happen, and a per-tool filter lets you look at Claude alone or next to Codex, Cursor and Copilot.

It is free and open source, runs on Windows, macOS and Linux, and needs no account for local tracking. A free account adds cloud save so your history follows you to a new computer.

Why it ranks first: the longest view of your own numbers with the least effort.

2. /stats inside Claude Code

/stats opens the Stats tab of /usage. On Pro, Max, Team and Enterprise plans the breakdown switches between the last 24 hours and the last 7 days with d and w. Anthropic notes the figures are approximate and limited to this machine.

Why it ranks second: built in, zero setup, but a one-week horizon.

3. ccusage

ccusage is an open-source CLI. Run npx ccusage@latest and it prints daily, weekly, monthly or per-session tables from local Claude Code files, with --json output for scripts.

Why it ranks third: the best pick when you want statistics in a file or a pipeline. It reads Claude Code transcripts, which are deleted after 30 days by default, so it cannot see further back than the files on disk.

4. Team and Console dashboards

On Team and Enterprise plans, admins get an analytics dashboard and a spend report with CSV export. API organizations get a Claude Code dashboard in the Claude Console and the Claude Code Analytics API with daily per-user metrics.

Why it ranks fourth: strong for managers, out of reach for most individual developers.

5. Your billing pages

The Console usage page, Settings > Usage on claude.ai for usage credits, or your cloud provider's billing console show real charges.

Why it ranks fifth: authoritative for money, thin on tokens and models.

The ranking at a glance

Rank Tool Time range Export Setup
1 UsageAtlas Every recorded day No Install the app
2 /stats 24 hours or 7 days No None
3 ccusage Transcripts still on disk JSON One command
4 Team and Console dashboards Organization history CSV or API Admin access
5 Billing pages Billing periods Varies Account access

Which one to use

Start with UsageAtlas for day-by-day statistics you can return to next month. Keep /stats for a glance during a session, reach for ccusage when the numbers need to leave your machine as JSON, and treat the billing pages as the final word on what you paid. UsageAtlas cost figures are estimates, not invoices.