How to check Claude Code usage

Claude Code records everything it does, but the numbers are spread across a few places: two built-in commands, a directory of local log files, and (for API users) the Anthropic Console. This guide covers each layer and the open-source tools built on top of them.

Built-in commands

/usage shows your plan's rate-limit status — how much of the current session window and weekly cap you've consumed. If you're on Pro or Max, this is the source of truth for "how close am I to the limit."

/stats opens a usage dashboard: sessions, token totals, a model breakdown, and an activity heatmap. It's the quickest way to get a historical picture without installing anything.

If you pay per token with an API key, /cost reports what the current session has spent, and the Anthropic Console has account-level cost history.

The local logs everything else builds on

Claude Code writes JSONL session logs under ~/.claude/projects/ (or ~/.config/claude/projects/). Each entry includes the model, input/output/cache token counts, and timestamps. No third-party service is involved — every tool below works by reading these files.

CLI reports: ccusage

ccusage is the most widely used reporting tool. It reads your local logs and prints daily, monthly, per-session, or 5-hour-block tables, with cost estimated at public API pricing:

npx ccusage            # daily report
npx ccusage monthly    # monthly totals
npx ccusage blocks     # 5-hour billing windows

It's local-only: nothing is uploaded anywhere. If all you want is your own numbers, ccusage plus the built-in commands is a complete setup.

Real-time limit monitoring

For a live view while you work — burn rate, predicted time until you hit the session limit — Claude Code Usage Monitor runs a terminal dashboard with predictions and warnings. A custom status line can also surface token counts in the Claude Code UI itself.

Seeing usage across a group

The layers above are single-machine. To see usage across people, there are two routes:

Team / Enterprise plans have admin usage analytics in the Claude console — per-member usage by product and model. The official option if your org pays for seats.
ccclub (our project) is the informal option: everyone runs npx ccclub init / join, and the group shares one leaderboard of tokens, estimated cost, and agent mix — covering Codex, OpenCode, Amp, and pi-agent too. Only aggregated numeric summaries are uploaded (no prompts, code, or file paths; ccclub show-data shows the exact payload). It's the right tool for friends comparing usage, not for compliance reporting.

A note on "cost" when you're on a subscription

On Pro/Max you don't pay per token, so every tool that shows dollars (ccusage, ccclub, and others) is showing the API-equivalent value of your tokens at public pricing — useful for comparing against your subscription price, but it is not a bill.

FAQ

How do I see my Claude Code usage quickly?

Run /usage inside Claude Code for your current rate-limit status, or /stats for a dashboard of sessions, token totals, and a model breakdown. Neither requires installing anything.

Where does Claude Code store usage logs locally?

In JSONL files under ~/.claude/projects/ (or ~/.config/claude/projects/). Each entry records the model and token counts. Tools like ccusage and ccclub read these files locally.

How can I see Claude Code costs if I'm on Pro or Max?

Subscriptions don't bill per token, so tools estimate the API-equivalent value of your usage at public API pricing. ccusage reports it locally; ccclub additionally shows how that value compares to your plan price (Monthly ROI).

Can I see my teammates' Claude Code usage?

On Team/Enterprise plans, admins get official usage analytics. Otherwise, each person can opt into a shared leaderboard: ccclub syncs aggregated numeric summaries from local logs into a private group board — no accounts, and no prompts or code are uploaded.

Do usage-tracking tools upload my code or prompts?

The local log files do contain conversation data, but reporting tools only read the usage metadata. ccusage never uploads anything. ccclub uploads only numeric summaries (tokens, estimated cost, model names, turn counts) — you can verify with ccclub show-data.

Last updated 2026-07-07. Corrections welcome on GitHub.