OpenUsage

Track your AI coding subscriptions from the macOS menu bar.

OpenUsage shows how much of each AI plan you have used: session and weekly limits, credits, and balances, in one panel. Star the metrics you watch most and they appear in the menu bar.

You add each account in the app. OpenUsage reads nothing that belongs to other tools: no Keychain items, auth files, logs, databases, or environment variables. It shows only the limits and dollar values that the provider's own API reports, except ChatGPT's credits, which also show their dollar value at 4¢ a credit.

Installation

Homebrew:

brew install --cask openusage

Direct download: download the latest universal DMG from the releases page, open it, and drag OpenUsage to your Applications folder.

Either way, the app updates itself in place through signed, notarized Sparkle updates. Requires macOS 15 (Sequoia) or later.

Accounts

Open Accounts from the panel's Options menu (or press Return), click +, and click a provider to start its sign-in. Browser sign-in opens your browser; Open Browser opens it again and Copy Link lets you pick another browser. Device-code sign-in shows the code to enter. API-key sign-in links to the page where you create the key. You can add several accounts for the same provider. See Accounts for renaming and removing accounts.

Account names and settings live in the app's own preferences. OAuth tokens and API keys live in the app's own Keychain service.

Providers

Claude, ChatGPT, Cursor, Antigravity, Copilot, Grok, Ollama, OpenCode, OpenRouter, and Z.ai. Claude, ChatGPT, Cursor, Antigravity, Copilot, and Grok sign in with OAuth. Ollama, OpenCode, OpenRouter, and Z.ai use API keys. OpenRouter's balance needs a Management key. Providers lists what each one shows and what each sign-in grants.

Features

• Menu bar stars. Star up to two metrics per provider. When more than one account of a provider is

• Dashboard. A header and a card per provider. The header shows the provider's logo and name, and

• Resets. Claude and ChatGPT accounts show a Limit Resets row with the number of available rate-limit

• Share. Rest the pointer on a provider's header and click the copy button at its right, or

• Notifications. Optional alerts when a limit falls under 10% or your pace changes.
• Global shortcut. Toggle the panel from anywhere.
• Command line. Install the openusage command from Settings; it prints the usage

• Automatic updates. Signed, notarized in-app updates, with an optional beta

Documentation

Behaviour docs live in docs/: the dashboard, accounts, the menu bar, settings, the command line, refreshing, providers, updates, and privacy.

For working on the code, see architecture, adding a provider, and debugging.

Requirements

• macOS 15 (Sequoia) or later
• Universal binary, for Apple Silicon and Intel Macs

Building

swift build                 # debug build
script/test_quiet.sh        # run the test suite without it taking the keyboard or the screen
./script/build_and_run.sh   # build and launch the dev app from dist/ (no install)

script/test_quiet.sh takes swift test arguments such as --filter.

The dev app is staged as dist/OpenUsage.app with the bundle identifier com.robinebers.openusage.dev, so it runs beside an installed OpenUsage and never checks for updates.

Architecture

SwiftPM package, SwiftUI content hosted in an AppKit-owned NSStatusItem and a key-capable NSPanel, Swift 6 strict concurrency. AccountStore persists accounts, CredentialVault stores their credentials, ProviderLogin signs in, and one AccountProviderRuntime per account fetches usage and maps it to metric lines. See the architecture overview and AGENTS.md for conventions.

Releasing

Releases are automated: pushing a v* tag on main builds, signs, notarizes, and publishes a new version. A plain tag (v0.8.0) ships to everyone; a pre-release suffix (v0.8.0-beta.1) ships to the beta channel. The pipeline lives in .github/workflows/release.yml, and the step-by-step is in the release-swift skill.

Release setup (one-time)

The release workflow needs these repository secrets (Settings → Secrets and variables → Actions):

| Secret | What it is | | ---------------------------- | --------------------------------------------------------------------- | | APPLE_CERTIFICATE | base64 of your Developer ID Application .p12 | | APPLE_CERTIFICATE_PASSWORD | the password set when exporting that .p12 | | APPLE_ID | the Apple ID email used for notarization | | APPLE_PASSWORD | an app-specific password for that Apple ID | | APPLE_TEAM_ID | your Apple Developer team ID | | SPARKLE_PUBLIC_KEY | base64 EdDSA public key, baked into the build as SUPublicEDKey | | SPARKLE_PRIVATE_KEY | base64 EdDSA private key used to sign the DMG | | POSTHOG_CLI_API_KEY | PostHog personal API key used to upload dSYMs for crash symbolication | | POSTHOG_CLI_PROJECT_ID | numeric PostHog project ID the dSYMs upload to |

Export the Developer ID Application cert (with its private key) from Keychain Access as a .p12, then base64 -i DeveloperID.p12 | pbcopy. App-specific passwords come from appleid.apple.com → Sign-In and Security → App-Specific Passwords. Generate the Sparkle EdDSA key pair once with Sparkle's generate_keys tool; the public and private values must be a matching pair or signing is silently skipped.

The two POSTHOG_CLI_* secrets only upload debug symbols (dSYMs) so PostHog can symbolicate crash reports. POSTHOG_CLI_API_KEY is a PostHog personal API key (PostHog → Settings → Personal API keys) and POSTHOG_CLI_PROJECT_ID is the numeric ID from your project URL. The upload host is hardcoded in the workflow (https://us.i.posthog.com). These two do not block a release: if POSTHOG_CLI_API_KEY is unset the workflow skips the upload with a warning, and crash reports for that version show raw addresses instead of symbolicated stack traces.

The repository must be public (Sparkle fetches the DMG and appcast anonymously), and the appcast is served from GitHub Pages. Confirm Settings → Pages points at the gh-pages branch after the first release.

Contributing

Issues are welcome. Pull requests are strict and issue-first: comment on an issue, wait for a maintainer to add the approved label and assign it to you, then reference it in your PR with Fixes #123. Automation closes external PRs without an approved issue assigned to their author, and warns when an accepted PR adds more than 1,000 lines. Read CONTRIBUTING.md before opening one. Report security issues privately per SECURITY.md. The OpenUsage name and logo are covered by the trademark policy.

License

MIT