whoburnedmore

who burned more tokens — you or them? One command reads your local AI coding-agent usage logs, adds up your burn, and puts you on the public leaderboard with a shareable dashboard.

npx whoburnedmore

That's the whole thing. No install, no config. Your first run signs you in — the CLI opens a page, you approve a short code, and this machine is bound to your account.

What you'll see

whoburnedmore · https://whoburnedmore.com

  🔥 your burn report

  claude         2.26B tokens   $2,640.07    19 days
  codex          58.2M tokens      $16.85     5 days
  ──────────────────────────────────────────────
  total          2.31B tokens   $2,656.91
  today          92.8M tokens

  You burned 2.31B tokens. Your dashboard:
  https://whoburnedmore.com/u/<your-handle>

  Re-run anytime to update it. Background sync keeps it fresh every 15 min.

Once you're signed in, your usage lands on the leaderboard under your handle. Run the command again anytime to refresh — or let the background sync do it for you.

Want to stay off the board? Run npx whoburnedmore private to hide your dashboard, or npx whoburnedmore --local to never upload anything at all.

Privacy first

Only daily aggregate numbers ever leave your machine — date, tool, model, token counts, and estimated cost. Never your prompts, your code, or your file names.

See exactly what would be sent, and send nothing:

npx whoburnedmore --dry-run

Or stay completely offline — --local builds the same dashboard as a self-contained HTML file on your machine and opens it in your browser, sending nothing anywhere and never signing you in:

npx whoburnedmore --local

Commands

| Command | What it does | | --- | --- | | npx whoburnedmore | Sign in, submit your burn, land on the leaderboard, open your dashboard | | npx whoburnedmore --board=CODE | Compare with friends — sign in and join their board | | npx whoburnedmore --org=SLUG | Submit to your organization's board (companies / hackathons) | | npx whoburnedmore --local | Build the dashboard locally and open it (fully offline, no sign-in) | | npx whoburnedmore --dry-run | Print exactly what would be sent, send nothing | | npx whoburnedmore --no-submit | Print local stats only, send nothing | | npx whoburnedmore private | Hide your dashboard from the leaderboard | | npx whoburnedmore public | Put it back on the leaderboard | | npx whoburnedmore remove | Delete your dashboard and all its data | | npx whoburnedmore verify | Delisted? Re-verify your usage to get back on | | npx whoburnedmore link --token=TOKEN | Bind a server / VM to your account (token from your profile) | | npx whoburnedmore daemon | Keep syncing in the foreground (containers with no scheduler) | | npx whoburnedmore status | Check background-sync health (last sync, staleness) | | npx whoburnedmore install-sync | Turn the 15-minute background sync back on | | npx whoburnedmore uninstall-sync | Turn the background sync off |

Supported tools

Usage is read via ccusage from any of these agents you use locally:

claude · codex · gemini · copilot · opencode · amp · droid · goose · kimi · qwen · kilo · openclaw · hermes · pi · codebuff

Whatever you have logs for is picked up automatically — you don't pass any flags.

Compete with friends and teams

• Friends: join someone's board with npx whoburnedmore --board=CODE (the code comes from their board's invite).
• Companies / hackathons: submit to an organization board with npx whoburnedmore --org=SLUG (add --pass=CODE if the org requires a join code).

Your submissions link to your handle at whoburnedmore.com/u/<handle>. You can delete your account and every row of data anytime from your profile.

Keep it live

Background sync is on by default after your first run, so your dashboard stays fresh without re-running by hand. To manage it:

npx whoburnedmore status           # last sync + staleness
npx whoburnedmore uninstall-sync   # turn the background sync off
npx whoburnedmore install-sync     # turn it back on (launchd / cron / scheduled task)

The installed background job runs the latest published whoburnedmore package on each sync tick, so future CLI fixes are picked up automatically after the next 15-minute refresh.

Servers & VMs

Generate a one-time link command from your profile on whoburnedmore.com and run it inside the machine to bind it to your account:

npx whoburnedmore link --token=TOKEN

On a persistent VM, background sync uses cron or a systemd user timer automatically. In a container or any host without a scheduler, run npx whoburnedmore daemon under your process manager instead. Set WHOBURNEDMORE_CONFIG_DIR to a persistent path so the machine identity survives restarts.

Links

• 🏆 Leaderboard — whoburnedmore.com
• 📊 Your dashboard — printed in the terminal after your first run

Requirements

Node.js >= 20.

License

MIT © Arham Wani