# Coding-agent usage tools compared

Last updated: 2026-07. Descriptions are based on each project's public
documentation; check the linked sites for current details.

These tools solve related but different problems. Short version: ccusage is
for looking at your own numbers, monitors are for watching limits in real
time, viberank/ccgather are public rankings, and ccclub is a private
leaderboard for a group of friends.

| Tool | What it does | Sharing model | Account needed |
|------|--------------|---------------|----------------|
| [ccusage](https://ccusage.com) | CLI reports of your own local usage (daily / monthly / per-session / billing blocks) across many coding CLIs | None — local only | No |
| [Claude-Code-Usage-Monitor](https://github.com/Maciek-roboblog/Claude-Code-Usage-Monitor) | Real-time terminal monitor with limit predictions and warnings | None — local only | No |
| [viberank](https://www.viberank.app) | Public community leaderboard; you submit your usage data | Public ranking | Yes (GitHub) |
| [ccgather](https://ccgather.com) | Public community leaderboard with country/global stats | Public ranking | Yes |
| [ccclub](https://ccclub.dev) | Private leaderboard for a group of friends; auto-syncs from local logs of Claude Code, Codex, OpenCode, Amp, and pi-agent | Private groups; opt-in global board | No |

## Where ccclub fits

- You want to compare usage **with specific people you know**, not the world.
- You want it to update automatically (session-end hook + background sync)
  instead of manually submitting.
- You care that only numeric summaries leave the machine (no prompts, code,
  or file paths — `ccclub show-data` shows the exact payload).

## Where ccclub doesn't fit

- You only want your own numbers: use ccusage or Claude Code's built-in
  `/usage` and `/stats`.
- You want real-time limit tracking: use a live monitor.
- You want maximum public visibility: viberank and ccgather are built for
  that.

ccclub is open source (MIT): https://github.com/mazzzystar/ccclub