Guides

Practical notes on tracking coding-agent usage — no fluff, dated, kept current.

Claude Code usage, explained

What a Claude Code usage number counts — input, output and cache tokens — why cache dominates the total, and how to read it per day, week or agent.

How to check Claude Code usage

Check Claude Code usage in order: the built-in /usage screen, the local transcripts, then ccclub for a dated history — and how to read what you get.

Claude Code limits, explained

How Claude Code rate limits work on Pro and Max — the 5-hour rolling window, weekly caps, when each one resets — and how to see exactly where you stand.

Claude Code cost, and what the number means

How a Claude Code cost figure is built — list-price table, the four token buckets, provider-reported costs — and why on a subscription it is not a bill.

Claude Code statusline: what ccclub puts there

A Claude Code statusline showing model, effort, your 5h and 7d limit percentages and your group rank — drawn from cache, with no network call to render.

How to track Codex usage

Check Codex usage with /status, find the session logs in ~/.codex/sessions/, and see the tools that report Codex tokens — alongside Claude Code.

ccusage vs ccclub

ccusage reports your own local usage; ccclub is the ccusage alternative for a shared board — friends or a team ranked on one leaderboard, auto-synced.

Claude Code leaderboards, compared

Which Claude Code leaderboard is public and which stays private to friends or teammates: viberank, ccgather, tokenleaders and ccclub. (We build ccclub.)