Every token. Every model. Every trend.
Your AI coding history, parsed locally and aggregated into one browser dashboard. The live rate-limit side lives in the desktop pill below.
-
Six tools, one dashboard
Claude Code, Codex, Gemini CLI, OpenCode, Amp and Pi-Agent — all parsed from local files, aggregated into one view.
-
Every breakdown that matters
Daily timeline by provider. Cost-by-source donut. Top models ranking. Monthly trend. 90-day activity heatmap. Filter and drill into details by day.
-
Local-only, no API keys
Reads files your AI tools already write to disk. Nothing leaves your machine. No signup, no telemetry, no cloud.
Live limits, always visible.
A floating pill that pins your live Claude + Codex rate-limit windows and today's token use to the top of your screen. The historical side lives in the dashboard above. One click switches between them.
Three steps from zero to insight
No config files, no accounts, no setup. Your AI tools already write the data — TokenBBQ just reads it.
Run one command
No install needed. npx pulls the latest version and runs immediately. No env vars, no setup.
$ npx tokenbbq@latest
TokenBBQ scans your tokens
Auto-detects usage logs from six AI coding tools on your machine. Parses them in memory and fetches current model pricing from LiteLLM.
Dashboard opens locally
A localhost dashboard with charts, breakdowns and trends. Or pin the desktop pill and watch your limits live.
localhost:3000
Six AI coding tools
Auto-detected if the data exists on your machine. No config required.
Local-only. Auditable. No cloud.
Your AI tool logs contain code context, project names and session data. None of it leaves your machine.
-
Your token logs stay on your machine
Reads files on your filesystem from six AI tools. Aggregates them in memory. Serves a dashboard on localhost. None of it is uploaded.
-
Your claude.ai session, your machine
The pill reads live Claude rate limits by talking directly to claude.ai with your own session key. It's stored in your OS keyring (Windows Credential Manager / macOS Keychain), never through a TokenBBQ server, because there isn't one.
-
Open source, MIT, auditable
The entire codebase is on GitHub. Read it, fork it, audit it. Don't trust any tool you can't inspect.
Network requests on first launch:
claude.ai (rate limits, only if you connect a session key) ·
raw.githubusercontent.com (LiteLLM model prices) ·
cdn.tailwindcss.com + cdn.jsdelivr.net (dashboard styling).
That's the entire list.
Frequently asked
Quick answers for the things people search before they install.
How do I track my Claude Code token usage?
npx tokenbbq — it auto-finds your local Claude Code session files (no API key, no signup) and shows your token usage and remaining 5-hour and 7-day rate-limit windows. Or grab the desktop pill for the always-visible version.
Is there a ccusage alternative that supports more tools?
Can I monitor Claude Code rate limits on Windows?
How do I track Codex CLI usage too?
~/.codex/sessions/**/*.jsonl and pulls the weekly + 5-hour rate-limit values straight out of Codex's session log — shown next to your Claude data, with a toggle to switch between them.
Stop guessing. Start grilling.
One command. Six tools. Your data, your machine, your dashboard.
Or grab the desktop pill — Windows & macOS, no Node required.