Best Claude Usage Trackers for Mac (2026)
Disclosure: I built CapMeter, one of the apps below. I've tried to describe the others as accurately as I could from their own listings and sites — I haven't installed all of them myself, so if something below is wrong or out of date, tell me and I'll fix it.
The one thing to check before you pick one
These apps split into two families, and it matters more than any feature list: some read your Claude.ai account directly (your session, the same one your browser uses), and some only read local files that Claude Code writes to your Mac. If you mostly use Claude in a browser, the second kind won't show you anything — there's nothing local for it to read. If you only ever use Claude Code and never sign in on claude.ai, the first kind still works, since Claude Code shares the same account-level limits.
Apps that read your Claude.ai account
CapMeter — $9.99 once (launch price, regular $14.99; 14-day free trial), Mac App Store.
Reads your own logged-in Claude.ai session, so browser chats and Claude Code land in the same number. Turns your burn rate into a time estimate ("limit in ~1h 18m") instead of just a percentage, keeps 7/14/30/90-day history with CSV/JSON export, and can send threshold alerts to macOS notifications, Slack, Discord, or any webhook, with quiet hours to silence them at night. A floating widget stays visible across every Space. Supports multiple accounts. No subscription — one payment unlocks it permanently.
Usage for Claude — free to download, in-app purchases up to $17.99 or $5.99/month.
Also reads your Claude.ai account, with a broader device footprint: iPhone and Apple Watch widgets plus iCloud sync across them. Its history view is reported to include a prediction of when you'll hit your limit, though it's tucked into that screen rather than the main popup. No webhook alerts, no quiet hours, no floating widget. Longer comparison here if you're deciding between just these two.
Claude Usage Tracker — free, open source (MIT), installed via Homebrew.
Built by hamed-elfayome, with over 3,000 GitHub stars. Reads your Claude.ai session, plus Claude Code and the Anthropic API console — the widest data coverage of anything here. Shows a six-step color-coded pace indicator rather than a time estimate, and has no webhook alerts, quiet hours, or CSV/JSON export. The default pick if you want something free and don't need alerts or long-term history — more on when free stops being enough.
ClaUse Bar — free, Mac App Store.
Reads your Claude.ai login and supports switching between multiple organizations. No burn-rate prediction, no history, no export, no alerts beyond what's on screen. The simplest tool in this list, for someone who only wants the current percentage in the menu bar.
Apps that only work with Claude Code
These need the Claude Code CLI installed and read its local files — a browser conversation won't move their numbers at all.
SessionWatcher — $6.99 one-time for Claude alone, $14.99 for a bundle that adds Codex and Cursor, or $24/year for a Pro tier with 90-day history and multiple accounts.
Reads Claude Code's local session files directly. If you split time between claude.ai in a browser and Claude Code, this will only show you half the picture. Its own site runs a set of usage-tracking guides, which is where a lot of its search traffic comes from — worth a look regardless of which app you end up using. I wrote up a fuller side-by-side comparison if you're weighing the two directly.
Claude-God — free, open source, on GitHub.
Reads Claude Code's own login and local project files, and predicts when you'll hit your limit based on current velocity — conceptually close to a burn-rate estimate, but for Claude Code only. Ships WidgetKit gauges and a pinnable popover. An earlier version had a bug where it consumed Claude Code's own refresh token, forcing extra logins; later releases fixed it.
Which one should you pick
If you want free and don't mind a plain interface, Claude Usage Tracker is the widest free option and covers the most data sources. If you only ever use Claude Code and want one tool across several AI CLIs, SessionWatcher's bundle is built for exactly that. If you want alerts to actually reach you somewhere other than the menu bar, a widget that survives switching desktops, and one account-level number that covers both a browser and a terminal, that's the gap I built CapMeter to fill.
Whichever you pick, the more useful test is simpler than any feature table: open it once, right before you'd normally hit your limit, and see if it told you anything you didn't already know from staring at the percentage.