ccusage vs ccclub
Short answer: they solve different problems, and plenty of people use both. ccusage answers "what did I use?"; ccclub answers "how does our group compare?". Disclosure up front: ccclub is our project — we'll try to be even-handed anyway.
What each tool does
ccusage is a reporting CLI. It reads local coding-agent logs and prints tables — daily, monthly, per-session, or 5-hour billing blocks — with cost estimated at API pricing. It supports a long list of coding CLIs, runs entirely offline, and uploads nothing. It has become the de-facto standard for personal usage reports.
ccclub is a shared leaderboard. Everyone in a group runs npx ccclub init or join CODE; after that, usage syncs automatically (a session-end hook for Claude Code, background sync for Codex, OpenCode, Amp, and pi-agent) and the group sees one ranking — in the terminal via ccclub or on a live web dashboard. It uploads aggregated numeric summaries only: token counts, estimated cost, model names, turn counts, in 30-minute blocks. No prompts, code, or file paths; ccclub show-data prints the exact payload.
Side by side
| ccusage | ccclub | |
|---|---|---|
| Core question | What did I use? | How does our group compare? |
| Data leaves your machine | Never | Numeric summaries only |
| Account required | No | No (6-letter invite code) |
| Report granularity | Daily / monthly / session / 5-hour blocks | Today / yesterday / 7d / 30d / all-time |
| Web dashboard | No (terminal tables) | Yes, live per group |
| Auto-sync | n/a (run on demand) | Yes (hook + background) |
| Agent coverage | Very broad (15+ CLIs) | Claude Code, Codex, OpenCode, Amp, pi-agent |
| License | MIT | MIT |
Pick ccusage if…
- You want reports for yourself and nobody else needs to see them.
- You need coverage for an agent ccclub doesn't support yet.
- You want fine-grained analysis (per-project, per-session, billing blocks).
Pick ccclub if…
- You and friends or teammates want one leaderboard that stays current without anyone manually running reports.
- You want a shareable live dashboard (each group gets
ccclub.dev/g/CODE). - You're curious how your usage ranks more broadly — there's an opt-in global board.
Or use both
They read the same local logs and don't conflict. A common setup: ccusage for detailed personal analysis, ccclub for the group scoreboard. If you're deciding among leaderboard tools specifically, see the leaderboard comparison.
FAQ
Is ccclub a replacement for ccusage?
No. ccusage is a local reporting tool for your own usage; ccclub is a shared leaderboard for a group. They read the same local logs and many people use both.
Does ccclub upload more data than ccusage?
ccusage uploads nothing. ccclub uploads aggregated numeric summaries (tokens, estimated cost, model names, turn counts in 30-minute blocks) so the group board can update — never prompts, code, or file paths. Run ccclub show-data to see the exact payload.
Which supports more coding agents?
ccusage covers more CLIs overall. ccclub currently supports Claude Code, Codex, OpenCode, Amp, and pi-agent — the ones it can sync into a shared leaderboard.
Can I use ccclub just for myself?
Yes — a group of one works, and the all-time view makes it a simple personal history. But if you never want a shared board, ccusage alone is the simpler tool.
Last updated 2026-07-07. Corrections welcome on GitHub.