Know you're about to hit
your Claude limit — before you do

CapMeter watches how fast you're burning through your Claude or Codex session — browser and CLI alike — and tells you when you'll run out.

For Claude & Codex accounts

Free 14-day trial — then $9.99 once, no subscription

Opens in demo mode without an account — look around before signing in. · Privacy Policy

Predicts & warns — not just a number
Fully local — Keychain-encrypted, no servers
Menu bar app — macOS 12+, Apple Silicon
$9.99 once — no subscription
Live demo

Watch it track Claude usage — right on your desktop

An interactive recreation of the app — scroll to step through it.

Finder File Edit View Go Window Help
38%
New chat
Recents
Refactor auth flow
Draft launch email
Explain vector DBs
SQL query help
Can you rewrite this function to use async/await and add error handling?
Here's the refactored version using async/await with proper error handling and retries:
async def fetch_data(url):
  try:
    async with session.get(url) as r:
      return await r.json()
  except ClientError as e:
    logger.warning(f"retry: {e}")
The key changes: the call is now non-blocking, and network failures are caught and logged instead of crashing.
Nice. Can it retry a few times before giving up?
Sure — wrap it in a loop with exponential backoff so each retry waits a little longer:
for attempt in range(3):
  try:
    return await fetch_data(url)
  except ClientError:
    await asyncio.sleep(2 ** attempt)
This gives it three attempts with 1s, 2s, then 4s waits — enough to ride out most transient network blips.
Send a message…
38
3h 49m left
⚡ limit in ~1h 18m
Extra usage ~$3.20/hr $17.00 left
Acme Team — Slack
Acme A
Channels
# general
# alerts
# dev
# random
# alerts ·  usage notifications
D
Devon 1:40 AM
shipping the release now 🚀
CapMeter APP 2:09 AM
⚡ CapMeter — 80% threshold reached
▰▰▰▰▰▰▰▰▱▱80%
👤 you@example.com  ·  ⭐ Claude Pro  ·  🔄 Resets at 05:20
Image
Claude — 80% used now
Current session is running low. Resets at 05:20 AM.
Full breakdown in one click
Session %, burn rate, and exact time until reset
How it works

Install, open, done

1

Download from the App Store

Free for 14 days. Just install and open.

2

It reads your session locally

No API key. You sign in once on Claude's or OpenAI's own page — the session stays encrypted on your Mac.

3

See your limits in real time

A live ring in your menu bar and a floating widget show exactly how much session you have left — for Claude, Codex, or both.

Features

More than a live percentage

The number itself is the easy part. CapMeter is built around what comes after it — seeing the limit coming, and telling you somewhere you'll actually notice.

Limit prediction

CapMeter measures your burn rate and turns it into a time — "limit in ~1h 18m" — so you pace yourself instead of getting cut off mid-thought. It's an estimate from your recent pace, updated as you go.

Alerts that reach you

Get warned at your own thresholds — as a macOS notification or pushed straight to Slack & Discord. Set quiet hours so you're never pinged while you sleep.

Floating widget

A draggable mini-widget that floats above every window and Space — your remaining session always in view. When pay-as-you-go credits are on, it adds a second line tracking your spend rate and balance.

All your usage windows

Your current session (5-hour), your weekly window, and any per-model weekly limits your account reports — each as its own row with its own countdown. Claude's model names come straight from Claude, so new ones appear on their own. Browser and CLI draw from the same account limits — Claude Code and claude.ai, or Codex and ChatGPT — and both land in one counter.

History & export

7, 14, 30 and 90-day charts, weekly comparison and streaks — for usage percentage and separately for extra usage or credits. Export everything as CSV or JSON whenever you want.

Claude and Codex, one popup

Add Claude and Codex accounts side by side, each tracked independently with its own history. Switch between them without opening a browser — no more juggling two menu bar apps.

Live menu-bar ring

The baseline, done right: a color-coded ring shifts green → orange → red as you approach the limit. Always visible, zero clicks.

A closer look

Right where you work

A rich popup one click away in the menu bar.

CapMeter history view: 7, 14, 30 and 90-day usage charts with weekly comparison

History & trends
7, 14, 30, 90-day charts, streaks & export

CapMeter alert settings: usage thresholds, quiet hours, Slack and Discord webhooks

Alerts your way
Thresholds, quiet hours, Slack & Discord

Switching between multiple Claude and Codex accounts in the CapMeter menu bar popup

Multiple accounts
Claude & Codex, switch in one click

Your data stays on your Mac

CapMeter reads usage from your own Claude.ai or Codex session and keeps everything on-device. Your session credentials are encrypted in the macOS Keychain, and the app talks only to claude.ai or chatgpt.com — plus any Slack, Discord or HTTP webhook you set up yourself. No servers of ours, no analytics, no tracking, no backend. It never accesses your conversations.

You don't have to take that on trust: the app is sandboxed by the Mac App Store, and a network monitor like Little Snitch will show you the only host it ever contacts.

Pricing

Try it free, then pay once

Download free and use every feature for 14 days. One in-app purchase unlocks it for good — no subscription.

🔥 Launch offer
$14.99
$9.99
Save 33%

One-time unlock · after a free 14-day trial · No subscription

Coming soon to the Mac App Store

The menu-bar ring, your session and 7-day windows and the frosted glass theme keep working without the unlock — the list above is what the purchase adds.

Coming soon on the Mac App Store

Requires an active Claude.ai or Codex account · macOS 12+

Questions

The things you're probably wondering

Does my Claude Code usage count too?

Yes. Anthropic's own docs put it plainly: "Both Pro and Max plans offer usage limits that are shared across Claude and Claude Code, meaning all activity in both tools counts against the same usage limits." CapMeter reads your account-level usage, so terminal work and browser chats land in the same number.

You get the one number your limit actually runs on, not a split by client.

How is this different from claude /usage?

/usage is computed from local session history on that machine — Claude Code's own wording — so other devices and your claude.ai usage aren't in it. CapMeter reads the account-level number instead, the one your limit actually runs on.

And it's there without being asked. /usage answers when you ask it, but you only think to ask once you're already worried.

Do I have to sign in to try it?

No. It opens in demo mode with sample data, so you can click through the popup, the history charts and the settings before connecting anything. Sign in when you want your own numbers in there.

Do I have to give it my Anthropic or OpenAI password?

No. CapMeter opens Claude.ai's or OpenAI's own sign-in page in a window and stays out of it: it puts no code into that page and reads nothing out of it, so what you type goes to Anthropic or OpenAI, not to the app. It never sees your password.

What it keeps afterwards is the session credentials your browser would hold anyway — encrypted with the macOS Keychain and stored only on your Mac. It still can't read your conversations.

Does it work with Codex or ChatGPT too?

Yes. CapMeter tracks Claude and Codex/ChatGPT accounts side by side, each with its own history, extra usage or credits, and notifications. Add one or the other, or both, and switch between them from the same popup without opening a browser.

Why $9.99 when there are free ones?

A free counter only helps while you're looking at it. CapMeter turns your burn rate into a time — "limit in ~1h 18m" — and then comes to find you: a macOS notification, or straight into Slack or Discord, while there's still room to do something about it.

Around that: 90 days of history you can export, and a widget that floats above every window and Space — with a live $/hour rate if you're on pay-as-you-go credits.

One payment, not a subscription — less than a month of Claude Pro, and free for the first 14 days. $9.99 is a launch price through October 13, 2026; it goes back up to $14.99 after that.

What happens when the 14 days are up?

Your menu-bar session counter keeps working — you don't lose the thing you installed it for. What locks is the layer on top — everything the unlock adds. The display falls back to the ring on its own, and refreshes drop to every 30 minutes.

Buy the unlock and everything picks up where it left off. Nothing is deleted in the meantime.

What if Anthropic or OpenAI changes how usage is reported?

Then that provider's numbers stop updating until I ship a fix through the App Store — the other provider keeps working normally, since each is read independently. It's the one dependency I can't design around, so it's the one I watch — and if it's something I can fix, getting it working again is the only thing I'd be working on. Your purchase doesn't change while that happens — you paid once, not monthly, and your history stays on your Mac.

Can I get a refund?

The safeguard that actually protects you is the trial: 14 days with every feature unlocked, before any money changes hands.

If you still want one after buying, purchases go through the App Store, so it's Apple's call rather than mine — you'd request it at reportaproblem.apple.com.

Is there a Claude usage tracker for Mac?

Several, and most of them are free. They read the same usage figures Anthropic reports and show you the percentage you have used.

CapMeter is the paid one, and the reason to pick it is what it does with that number rather than the number itself: it measures how fast you are consuming the session and turns that into a time, keeps a daily record so you can compare weeks, sends alerts to Slack, Discord or any webhook, and puts a countdown in a floating window that follows you across Spaces. If a live percentage is all you need, a free tracker will do. See the full comparison for what each one does differently.

How do I check my Claude quota?

Claude shows it under Usage in the web app, which works but means remembering to look — and by the time you think to look you are usually already worried.

CapMeter keeps your session and weekly quota in the macOS menu bar so it is in view while you work, and warns you at thresholds you set before you run out rather than after. See the step-by-step guide for the browser and terminal methods too.

How do I know when my Claude limit resets?

CapMeter counts down to it. Your session window and your weekly window reset on separate schedules, so the two rarely line up and a single "resets at" time doesn't tell you much. The popup shows both as live countdowns, the menu bar keeps the session one in view, and the floating widget ticks it down second by second while you work.

What happens when I hit my Claude usage limit?

Claude stops responding until the window resets — mid-task, if that's where you happen to be. There's no warning beforehand, which is the reason this app exists.

CapMeter's job is to make that moment predictable rather than sudden: it turns your burn rate into a time, "limit in ~1h 18m", and can alert you at thresholds you choose, so you can wrap up or switch to a lighter model while there's still room to.

Does it run on an Intel Mac?

No — Apple Silicon only, macOS 12 or later. Mac App Store builds aren't thinned, so shipping a universal binary would make every M-series user download an Intel slice they'd never run. The App Store will simply tell you it's not compatible rather than letting you buy something that won't install.

The trial settles this better than a landing page can: 14 days with everything unlocked, before any money changes hands.

Get on the App Store

System requirements: macOS 12.0 Monterey or later · Apple Silicon (M1 or later) · Requires an active Claude.ai or Codex account