Skip to content
aka-cronosPublic

About

macOS menu bar app that shows your Claude, Codex, Cursor and Antigravity usage limits and when they reset.

Topics

Resources

Contributing

Security policy

Stars

9 stars

Watchers

0 watching

Forks

Repository files navigation

Uzzy

Your AI tools have limits. Checking them shouldn’t be a task.
See how much you’ve used, how much is left and when your usage limits reset—for Claude, Codex, Cursor and Antigravity, in one menu bar panel.

uzzy.app · Download

macOS 27 Apple Silicon Swift MIT license

The Uzzy panel open from the menu bar, with one card each for Claude, Codex and Cursor and each account's plan next to its title. Each usage limit has its own bar, its used percentage and its reset time; the Claude card also shows the usage credits spent this month, and the Codex card a badge with its banked resets.

Why Uzzy

Keep using Claude, Codex, Cursor and Antigravity. Uzzy brings their usage limits together so you can stop checking each one separately. It reuses the sessions Claude Code, Codex CLI, Cursor and Antigravity already keep on your Mac: no extra sign-in, no API key to paste.

Features

  • Four tools. One quick check. Open Uzzy from your menu bar to see Claude, Codex, Cursor and Antigravity together, with a separate card for each enabled provider, led by its logo and showing its plan.
  • Different limits stay different. Check each usage limit («5 horas», «Semanal», «Cursor Models», «Gemini · Semanal»…) on its own, with its reset in local time, a countdown and how long ago it was last read. A limit you haven't used yet shows no reset, since its period only starts with your first use. Five-hour and weekly limits are never blended into one number, and usage credits, credit balances and banked resets are shown next to them.
  • Checks while you look. Uzzy refreshes readings as you open the panel (unless the last reading is under five minutes old), then every five minutes while it stays open, and on demand with the refresh button. Close it and the requests stop, unless you turn on background refresh in Settings.
  • Alerts, if you want them. With background refresh on, Uzzy checks your usage limits every 5, 10, 15 or 30 minutes while the panel is closed, reusing the session it last read when you opened the panel, so it never asks for Keychain access on its own. It can notify you when a usage limit nears a threshold you choose, when it reaches 100%, and when a limit at 100% resets and can be used again. Everything is off until you turn it on.
  • Missing doesn’t mean zero. If a session expires or a provider can’t be reached, Uzzy tells you what happened (no session, expired session, offline, incompatible response…) and the other providers keep working. While the panel is open, an expired Claude, Codex or Antigravity session is read again every 30 seconds and picked up as soon as its app renews it; Cursor's is read again only when you open the panel or click Refresh. When a refresh fails, the card keeps the last valid reading and marks it as out of date.
  • Native settings. Organized into three tabs—General, Providers and Notifications—so you can choose whether the cards show how much is used or left, pick how detailed the countdown to a reset is and whether the resets available on an account are shown, turn the daily check for updates on or off, turn each provider on or off or change the order of the cards, and configure background refresh and usage limit alerts. The installed version and build are shown at the bottom of General.
  • Your language. The interface follows the system language: English or Spanish.

The Uzzy Settings window: a Used / Left switch for the percentage on the cards; the Claude, Codex and Cursor providers with buttons to reorder them and a switch to turn each one on or off; a Simple / Detailed switch for the time until a reset and a switch for the resets available; a switch to check for updates; and the installed version at the bottom.

Open Settings with ⌘, from the panel; ⌘W closes it and ⌘Q quits. Your choices are remembered across launches. A provider you turn off has no card, and Uzzy does not read its session or query its usage limits.

Supported providers

Provider Session it reuses What it shows
Claude Claude Code (the Keychain and ~/.claude.json) 5 hours, weekly, and weekly per model when the plan has them; the account’s banked resets; also the usage credits spent this month and their monthly limit («Créditos de uso»), when usage credits are on; the credit balance («Saldo de créditos») and cloud session credits with their expiry («Créditos para sesiones en la nube»), when the account has any
Codex Codex CLI signed in with ChatGPT (~/.codex/auth.json or $CODEX_HOME) 5 hours, weekly, any extra limit the plan has, the account's banked resets, and its credit balance when it has one
Cursor Cursor (its local state.vscdb, and its safeStorage key in the Keychain once you allow it) Weekly included usage on unified plans; «Cursor Models» and «Other Models» for the billing cycle on legacy plans; the credit balance when the account has one
Antigravity Antigravity, the app or the agy CLI (the Keychain), T3 Code's Antigravity agent (its token file), or the running app over 127.0.0.1 5 hours and weekly for each model group Google reports: «Gemini», «Claude and GPT», and any group a plan keeps apart, such as «Gemini 4 Argon»

Each card also shows the account's plan next to its title, e.g. «Claude · Max», when the provider reports a plan Uzzy knows: Claude Code keeps it in its Keychain item, Codex sends it with the usage limits, Cursor keeps it in state.vscdb and Google reports it for Antigravity («Google AI Pro» or «Google AI Ultra»).

Uzzy reads Claude Code's Keychain item through /usr/bin/security, the tool Claude Code writes it with. The item already trusts that tool, so macOS shows no Keychain prompt, even after Claude Code refreshes its token.

Antigravity keeps its Google sign-in in the Keychain too (service gemini, account antigravity), shared by the app and the agy CLI. Uzzy reads it the same way, through /usr/bin/security, and keeps only the access token and the account's email. When that Keychain token is missing or has expired, Uzzy checks two other read-only sources before reporting the session expired: first the freshest T3 Code Antigravity token file (~/.t3/userdata/providers/antigravity/<profile>/antigravity-acp/antigravity-oauth-token), and then a running Antigravity app's local service (stable or Insiders) over 127.0.0.1 using the local token from ~/.gemini/antigravity/daemon/hub_*.json or ~/.gemini/antigravity-insiders/daemon/hub_*.json. On that local path, no Google token is read or sent anywhere. If these sources belong to different accounts, the card shows whichever one has a fresh session. When every source is expired or unavailable, the card keeps its last reading, marked as out of date. Open Antigravity to renew it: while the panel is open, Uzzy reads the session again every 30 seconds, without querying Google until the token changes, and updates the card on its own. A usage limit you haven't touched in its period shows no reset: its period starts with your first use.

Since Cursor 3.27, Cursor encrypts its session in state.vscdb with a key it keeps in the Keychain (Cursor Safe Storage, account Cursor). That key also protects Cursor's other secrets, such as its MCP sign-ins, so Uzzy never reads it on its own:

  • The Cursor card asks first. Only after you click Allow Access does Uzzy read the key, and macOS may show its Keychain prompt. Uzzy reads the item itself, never through /usr/bin/security, so choosing Always Allow trusts Uzzy alone and no other program.
  • Uzzy uses the key only to decrypt the access token, then discards the key. The token stays in memory, like every other session, and is never written anywhere. Uzzy never reads the refresh token or Cursor's other secrets, and never changes the item or its access control.
  • Only opening the panel or clicking Refresh reads the key; automatic refreshes reuse the token already decrypted.
  • Turning Cursor off, or Revoke… in Settings, withdraws your consent and forgets the session; turning Cursor on asks again. If you chose Always Allow, macOS keeps trusting Uzzy until you remove it: open Keychain Access, search for Cursor Safe Storage (account Cursor), and remove Uzzy in Access Control.
  • A session Cursor stores unencrypted, as older versions do, is read as before, without the Keychain.

Privacy

  • Reuses, read-only, the sessions that already exist in Claude Code, Codex CLI, Cursor and Antigravity (including T3 Code's Antigravity token files under ~/.t3/userdata/providers/antigravity/ and Antigravity's local service files under ~/.gemini/antigravity/daemon/hub_*.json and ~/.gemini/antigravity-insiders/daemon/hub_*.json). It never asks for passwords, signs in, refreshes tokens or writes credentials. Cursor's encrypted session is read only after you allow it (see above).
  • Turning a provider off drops everything Uzzy held of its session (its token, account and figures) at once; turning it on reads the session again from the official app.
  • Only connects to api.anthropic.com, chatgpt.com, api2.cursor.sh and daily-cloudcode-pa.sandbox.googleapis.com to read usage limits, plans and credit balances, to 127.0.0.1 to ask a running Antigravity app on your Mac when no fresh token is available, and to api.github.com once a day to ask for the latest version. That check sends no token and nothing about you or your usage, and you can turn it off in Settings. No telemetry and no server of its own.
  • Usage data lives only in memory; nothing is written to disk.
  • Display magnitude, countdown style, whether to show resets available, which providers are turned on, provider order, background refresh and usage limit alert preferences, whether to check for updates and whether you allowed access to Cursor's key are stored in local UserDefaults; they contain no usage data, token, email or account identifier.

Install

Download Uzzy.dmg from uzzy.app or GitHub Releases, open it and drag Uzzy to Applications. It is signed with Developer ID and notarized by Apple, so it opens like any other app.

  • Requires macOS 27.0 or later on Apple Silicon.
  • Requires a signed-in session in Claude Code, Codex CLI (ChatGPT mode), Cursor and/or Antigravity.

To open it at login, add it under System Settings → General → Login Items.

Uzzy doesn't update itself. When a newer version is published, an Update button appears next to the name in the panel and downloads the new Uzzy.dmg; install it the same way.

To build it yourself, see CONTRIBUTING.md.

Contributing

See CONTRIBUTING.md. To report a vulnerability, see SECURITY.md.

Disclaimer

The endpoints the app uses to read usage data are internal and undocumented by the providers. They may change or stop working without notice, and each person is responsible for using them within their provider's terms.

Uzzy is an independent project, not affiliated with, endorsed by or sponsored by the makers of Claude, Codex, ChatGPT, Cursor or Antigravity. All product names and trademarks belong to their respective owners.

Acknowledgements

Endpoint research was informed by OpenUsage (MIT) and openai/codex (Apache-2.0). No code was copied from either.

License

MIT. See THIRD_PARTY_NOTICES.md for the providers' logos and the background photo.

About

macOS menu bar app that shows your Claude, Codex, Cursor and Antigravity usage limits and when they reset.

Topics

Resources

Contributing

Security policy

Stars

9 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages