Openusage is live · free · last verified 25 Oct 2026 · viability monitor
Openusage
OpenUsage is a free macOS menu bar AI limits tracker showing your Claude, Codex and Cursor session and weekly caps in one panel.
If you pay for Cursor Ultra, Claude Team 5x and Codex Pro and keep alt-tabbing between dashboards to ask "am I about to hit a wall?", OpenUsage answers it for free on your Mac. The localhost:6736 JSON API and `openusage` CLI are the parts paid trackers rarely match — your status line and agents read the same numbers the menu bar shows, with no auth to wire up. What you give up is breadth: macOS 15+ only, a beta line still refining the UI, and open-source maintainer support rather than an SLA.
Verdict generatedVerified 5d ago · liveness 69/100 · cite: rightaichoice.com/tools/openusage
- macOS developers paying for two or more AI coding subscriptions (Claude Code, Codex, Cursor)
- Power users who will curl localhost:6736 or call the openusage CLI inside scripts and status lines
- Developers running multiple Claude or Codex accounts who want them tracked side by side
- Open-source advocates who want MIT-licensed code, no account and no vendor lock-in
- Windows or Linux users — this is a macOS-native Swift app
- Anyone on macOS below 15, since the app requires macOS 15+
- Teams that need a vendor SLA or dedicated support contract
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip OpenUsage if you develop on Windows or Linux, or need per-request token logging and org-wide cost attribution across a whole engineering team — it's a macOS 15+ menu bar dashboard for subscription limits.
OpenUsage is free and MIT licensed, so the only cost is the AI subscriptions you're already paying for. Its real value scales with how many plans you run: one subscription is a nice ring, three or more (Claude Team 5x plus Cursor Ultra plus Codex Pro, for example) is where the 30-day cost ring and cross-provider limit view earn their place in your menu bar.
In short
Openusage — OpenUsage is a free macOS menu bar AI limits tracker showing your Claude, Codex and Cursor session and weekly caps in one panel. Best for macOS developers paying for two or more AI coding subscriptions (Claude Code, Codex, Cursor), Power users who will curl localhost:6736 or call the openusage CLI inside scripts and status lines, Developers running multiple Claude or Codex accounts who want them tracked side by side. Free to use.
What is Openusage?
Openusage — OpenUsage is a free macOS menu bar AI limits tracker showing your Claude, Codex and Cursor session and weekly caps in one panel. Best for macOS developers paying for two or more AI coding subscriptions (Claude Code, Codex, Cursor), Power users who will curl localhost:6736 or call the openusage CLI inside scripts and status lines, Developers running multiple Claude or Codex accounts who want them tracked side by side. Free to use.
OpenUsage is a free, MIT-licensed macOS menu bar app that tracks the session, weekly and monthly limits of every AI coding subscription you pay for, in one panel. It covers 11 providers — Claude, Codex, Cursor, Antigravity, Copilot, Devin, Grok, Ollama, OpenCode, OpenRouter and Z.ai — and shows the exact 5x session windows, weekly caps and total/Auto usage tied to each plan. You install it with a single Homebrew cask and it reads the credentials already on your Mac, so there is no account and no login. Cost rings break spend into today, yesterday and 30-day totals per provider, while pace markers and flame warnings flag when you are burning a limit faster than you should. Reset countdowns tell you exactly when the wall clears, and you can pin up to two metrics per provider to the menu bar or drag them into your preferred order. Multiple Claude and Codex accounts sit side by side, with usage history synced across Macs over iCloud. The part paid trackers rarely match is the local access layer: a REST API on localhost:6736 (schema openusage.limits.v1, no auth) and an `openusage claude` CLI that expose the same numbers the menu bar shows, so your status line, editor extension or agent can read them directly. A screen-share privacy mode hides your figures, and the provider system is plugin-driven so new AI tools can be added over time. Stable v0.7.15 and a beta line (v0.7.16-beta.1) are both downloadable. It is a native Swift and SwiftUI build for macOS 15+, aimed at developers who already juggle two or more AI coding subscriptions. Compared with metered token loggers and org-wide cost dashboards, OpenUsage is deliberately local and per-Mac — it is about knowing where you stand right now, not attributing spend across a team.
Key features
- Menu bar tracking for 11 providers: Claude, Codex, Cursor, Antigravity, Copilot, Devin, Grok, Ollama, OpenCode,
- Session, weekly and monthly limit progress bars per subscription plan
- Reset countdown timers per plan, e.g. "Resets in 1d 6h"
- Cost rings showing today, yesterday and 30-day spend per provider
- Pace markers and flame warnings when you burn limits too fast
- Pin up to two metrics per provider directly to the menu bar
- Drag-and-drop metric ordering with per-provider on/off toggles
- Multiple Claude and Codex accounts tracked side by side
- Usage history synced across Macs over iCloud
- Local REST API at localhost:6736 with schema openusage.limits.v1 and no auth
- openusage CLI (e.g. `openusage claude`) exposing the same limits data to scripts and status lines
- Credential reuse from your existing Mac setup — no account or login
- Screen-share privacy mode that hides your numbers
- Plugin-driven provider system for adding new AI tools
- Native Swift and SwiftUI macOS app, MIT licensed, installed via Homebrew cask
Behind the verdict
We reach for OpenUsage the moment a developer's stack crosses two AI coding subscriptions. The menu bar panel answers the one question that matters mid-task — how much session and weekly headroom do I have left, and when does it reset — without another browser tab. The cost rings and flame warnings add the bit most limit dashboards miss: not just where you are, but whether your current burn rate gets you to the reset. Pick it if you are on macOS 15+, you already run Claude Code, Codex and Cursor side by side, and you want a local, zero-login view. Pick it especially if you will actually use the REST API on localhost:6736 or the `openusage claude` CLI — feeding those numbers into a shell prompt or an agent is where it pays for itself. Pass if you are on Windows or Linux, on an older macOS, or if what you need is per-request token logging or org-wide cost attribution across a whole team. OpenUsage is per-Mac and local by design; it is not a team billing console. Against metered token loggers, the difference is intent: they reconstruct spend from logs, OpenUsage watches the limits the vendor actually enforces. Against a vendor's own usage page, it collapses eleven of them into one panel. The caveat is maturity — you are on a 0.x version where the beta channel is still refreshing the UI — so treat the polished edges as in progress.
Limitations
- OpenUsage is a macOS 15+ menu bar app with no Windows or Linux build, so mixed-OS teams can't standardise on it.
- A stable build (v0.7.15) and a beta line (v0.7.16-beta.1) run side by side, and beta builds may carry incomplete features.
- It is a measurement layer over 11 AI coding providers (Claude, Codex, Cursor, Antigravity, Copilot, Devin, Grok, Ollama, OpenCode, OpenRouter, Z.ai), not an AI model or coding agent, and it tracks subscription windows rather than per-request token logs.
- Support comes from open-source maintainers rather than a vendor support contract, and new provider coverage arrives through the plugin system at community pace.
as of 2026-10-20
Researching Openusage? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Openusage still active?
Openusage is live · free · last verified 25 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Openusage? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What's new in Openusage
Checked 10 days agoAcross the latest 2 updates: 1 feature update and 1 launch.
v0.7.6 Stable Release with Antigravity Support
The stable build adds Antigravity provider support alongside performance improvements and bug fixes, bringing the tracked provider count to 11.
v0.7.7-beta.1 Released
The beta channel introduces a refreshed UI and additional provider data options ahead of their move into a stable release.
What do users say about Openusage?
What people actually say about Openusage — is it worth it?
Our community sentiment research written Jul 30, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Openusage— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 25 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Openusage 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed description, features, integrations, summary, our verdict, pricing tiers
- — changed limitations, pricing page, platforms
- — changed switching in, limitations, our verdict, integrations, pricing tiers, features, summary, who should skip it, switching out, description, use cases, setup time, pricing fit
- — changed pricing tiers, description, summary, features
- — changed pricing page, limitations
- — changed who it suits, description, our verdict, features, who should skip it, pricing tiers, summary
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Openusage cost in 2026?
Openusage: Free to use. Pricing last verified 25 Oct 2026.
Plans compared
Every published Openusage tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| OpenUsage Stable | Free | — | macOS 15+ developers who want the proven build tracking Claude, Codex, Cursor, Antigravity and seven more providers with no beta surprises.Adds: Starting tier: current stable build v0.7.15 with all 11 provider trackers, the localhost:6736 REST API, the openusage CLI, menu bar pinning and screen-share privacy mode. |
| OpenUsage Beta | Free | — | Developers comfortable on a pre-release build who want the refreshed UI and new provider data options before they reach stable.Adds: Adds the v0.7.16-beta.1 build with early access to the refreshed UI and a preview of new provider data options, on the same free MIT-licensed terms. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Openusage's pricing actually pencils out — and where peers do it cheaper.
OpenUsage is free and MIT licensed, so the only cost is the AI subscriptions you're already paying for. Its real value scales with how many plans you run: one subscription is a nice ring, three or more (Claude Team 5x plus Cursor Ultra plus Codex Pro, for example) is where the 30-day cost ring and cross-provider limit view earn their place in your menu bar.
Has Openusage's pricing changed?
No plan price for Openusage has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Openusage?
Pick Openusage if you are macOS developers paying for two or more AI coding subscriptions (Claude Code, Codex, Cursor), Power users who will curl localhost:6736 or call the openusage CLI inside scripts and status lines, Developers running multiple Claude or Codex accounts who want them tracked side by side, Open-source advocates who want MIT-licensed code, no account and no vendor lock-in.
Look elsewhere if you are Windows or Linux users — this is a macOS-native Swift app, Anyone on macOS below 15, since the app requires macOS 15+, Teams that need a vendor SLA or dedicated support contract, Teams needing per-request token logging or org-wide cost attribution across many developers.
Skip it if Skip OpenUsage if you develop on Windows or Linux, or need per-request token logging and org-wide cost attribution across a whole engineering team — it's a macOS 15+ menu bar dashboard for subscription limits.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Openusage actually fits — and what changes day-one when you adopt it.
You run Claude Team 5x, Codex Pro and Cursor Ultra at once. You pin the Claude session and weekly windows plus the Cursor API usage metric to the menu bar and glance up before starting a refactor.
Outcome: You see Cursor Ultra API usage at 0% left before you kick off another agent run, and switch to Auto usage (98% left) instead of stalling halfway through.
You want your tmux status line and a custom editor extension to show Claude headroom without building a scraper. You point them at `curl localhost:6736/v1/limits`.
Outcome: The status line reads the same openusage.limits.v1 JSON the menu bar renders — no auth tokens, no polling a web dashboard, and a cron job can add threshold alerts on top.
You keep a personal and a work Claude account plus two Codex setups, and you're never sure which one has weekly headroom at the end of the month.
Outcome: Both Claude and Codex accounts sit side by side in one panel with history synced over iCloud, so you pick the account with capacity instead of guessing.
Use cases
- Watch your Claude Team 5x session window from the menu bar so a coding run doesn't die mid-file.
- Catch that Cursor Ultra API usage is at 0% left while Auto usage still has 98% before you start another task.
- See today's, yesterday's and 30-day dollar totals for Claude, Codex, Cursor and Grok in a single ring.
- Pipe `curl localhost:6736/v1/limits` into a status line, editor extension or agent so it reads the same numbers as the menu bar.
- Run multiple Claude and Codex accounts side by side and compare where the headroom is.
- Poll the local API from a cron job to build custom threshold alerts.
- Track 30-day spend across subscriptions to decide which plan to downgrade at renewal.
- Add a new provider through the plugin system instead of waiting on the core team.
Setup time & first value
How long it actually takes to get something useful out of Openusage — broken out by persona, not the marketing-page minute.
Most macOS 15+ users reach first value in a few minutes: `brew install --cask openusage`, launch it, and it reads the credentials already on your Mac — no account or login. Pin a metric or two per provider, then optionally wire `curl localhost:6736/v1/limits` into a status line.
Switching to or from Openusage
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a paid usage tracker (e.g. a per-key token logger): install with `brew install --cask openusage` and let it read existing Mac credentials, replacing a subscription-metering tool with a free MIT-licensed one.
- →From checking each vendor dashboard manually (Claude, Cursor, Codex): pin the session and weekly metrics per provider in the menu bar so the check becomes a glance instead of three tabs.
- ↗To a per-request token logger: if you need request-level accounting rather than plan windows, you'll need a separate metering tool, since OpenUsage tracks subscription limits and spend rings.
- ↗To a cross-platform tracker: if your team moves off macOS 15+, OpenUsage has no Windows or Linux build, so a web-based tracker becomes the replacement.
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Openusage”, and we withheld 5: 5 could not be judged, because “Openusage” is a single word that other videos use for other things. Showing the 1 we can prove is about Openusage.
Official links
What are the best Openusage alternatives?
The closest alternatives to Openusage we list are Dbeaver, Pump.co and Netron. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Dbeaver | Freemium | Pricing not published | — |
| Pump.co | Freemium | Pricing not published | — |
| Netron | Free | Free | — |
Alternatives to Openusage
View all
Tools that pair well with Openusage
Common stack mates teams adopt alongside Openusage, with the specific reason each pairing earns its keep.
Dbeaver
DBeaver Community is a free, open-source universal SQL client with an AI Chat that writes SQL from plain English.
Pump.co
Free cloud cost optimization for AWS, GCP, Azure and now AI inference spend — $0 platform fees, no cut of savings.
Netron
Free, open-source visualizer that renders neural network and ML model files as an interactive graph you can inspect layer by layer.
Openusage vs its closest rival
Openusage's closest head-to-head is with Spider Cloud — If you're a developer using multiple AI coding tools on macOS and want to track usage & costs without leaving your menu bar, OpenUsage is the perfect free, open-source companion. But if your primary need is feeding web data into AI agents or RAG pipelines at scale, Spider Cloud's all-in-one API with Silk extraction and flat-rate Unlimited plan is the clear winner. Choose based on whether your bottleneck is monitoring AI spend or acquiring structured web data. Verdict generated
Head-to-head comparisons
Openusage vs Spider Cloud
If you're a developer using multiple AI coding tools on macOS and want to track usage & costs without leaving your menu bar, OpenUsage is the perfect free, open-source companion. But if your primary need is feeding web data into AI agents or RAG pipelines at scale, Spider Cloud's all-in-one API with Silk extraction and flat-rate Unlimited plan is the clear winner. Choose based on whether your bottleneck is monitoring AI spend or acquiring structured web data.
GeneratedOpenusage vs Voyage Ai
These tools serve completely different needs. Pick Voyage AI if you need high-accuracy embedding and reranking for enterprise RAG on domains like finance or legal—be prepared to talk to sales. Choose Openusage if you're a macOS developer juggling multiple AI coding assistants and need a free, open-source way to track your usage and spending from the menu bar.
GeneratedOpenusage vs Temporal Ai
Choose Temporal AI if you need a rock-solid backend to make AI agents or microservices survive crashes, retries, and failures—it's the infrastructure behind OpenAI's reliability. Pick Openusage if you're a macOS developer juggling multiple AI coding tools and want a free, real-time dashboard to avoid hitting limits or overspending. They solve completely different problems: one builds resilient systems, the other tracks usage.
GeneratedFrequently asked questions
Used Openusage? Help shape our editorial sentiment research.