Ccclub

中文 | 日本語 | 한국어 | Deutsch | Français | Español

ccclub.dev

Claude Code and Codex leaderboard among friends. Track coding agent token usage, costs, active status, and agent mix across Claude Code, Codex, OpenCode, Amp, Grok, Pi, and Cursor.

Get Started

It asks your name, gives you a 6-letter code. Send it to friends:

Done. ccclub automatically detects supported coding agent logs on your machine and keeps usage synced. No config, no signup, no account.

Once a friend joins, check the leaderboard:

What gets uploaded

ccclub reads local usage logs that supported coding agents already write, bundles them into 30-minute summaries (agent source + token counts + cost), and uploads those numbers. No prompts, no code, no file paths, no project names — just counters. Run ccclub show-data to audit exactly what gets sent.

Supported sources:

If you use the default locations, there is nothing to configure. Custom locations are supported with CLAUDE_CONFIG_DIR, CODEX_HOME, OPENCODE_DATA_DIR, AMP_DATA_DIR, PI_AGENT_DIR, and GROK_HOME.

Cursor is opt-in

Cursor keeps no local token or cost logs, so it is the one source ccclub cannot read from disk. Collecting it means calling Cursor's own dashboard API (api2.cursor.sh) with the access token Cursor already stored in your macOS Keychain — so ccclub leaves it off until you ask:

Your Cursor token is never uploaded to ccclub; it only authenticates you to Cursor. The refresh token is never read, CURSOR_ACCESS_TOKEN overrides the Keychain lookup, and what syncs is the same aggregated block summary as every other source. If you never enable it, ccclub never reads the Cursor Keychain item and never contacts Cursor.

The leaderboard deliberately tracks coding agents only — usage from personal-assistant tools (e.g. OpenClaw) is excluded…