OpenUsage and OpenLimiter
The closest overlap, and the only other tool that designs for machine consumers.
- Platform
- macOS menu bar only. Requires macOS 15 Sequoia or later.
- Licence
- MIT
- Coverage
- Antigravity, Claude, Codex, Copilot, Cursor, Devin, Grok, OpenCode, OpenRouter and Z.ai.
- Source
- Both. Most providers are read from credentials already on your machine, some need a key you supply, and consumption is computed from local command line logs or an exported usage file.
What it does
It is a native Swift menu bar application that shows session limits, weekly limits, credits and spend for your AI coding subscriptions in one popover. It also publishes those limits as JSON on a local port so other software can read them.
What it does well
It is the only tool in this list whose documentation explicitly targets other programs: other applications read machine friendly limits from a local endpoint, and agents read stable limit JSON through the same cache. That is the same instinct OpenLimiter is built on, and OpenUsage got there first.
Where OpenLimiter differs
It stops at exposing the numbers and leaves every decision to whatever reads them. OpenLimiter turns the same numbers into an explicit advice policy with reason codes and injects them into an agent's prompt inside a declared untrusted data boundary. It also runs on Windows and Linux, which OpenUsage no longer does since its Swift rewrite.
Before you go looking
Four active repositories share this name. The one linked here is the project behind openusage.ai. A cross platform community fork, a terminal dashboard, and two Windows tray ports all exist separately.
How these were checked
These notes were read off each project's own repository, README or store listing in August 2026. Software moves, so check the source before you rely on any of it, and open an issue if something here has gone stale or is simply wrong.