Burning through your subscriptions too fast? Paying for stuff you never use? Stop guessing. OpenUsage is free and open source.
3.2k
Stars
324
Forks
25
Open issues
7
Contributors
AI Analysis
OpenUsage is a native macOS menu bar application that tracks usage across multiple AI coding subscriptions (Claude, Cursor, Codex, OpenRouter, Devin, Grok, and others), displaying session limits, weekly quotas, credits, and spending in a customizable dashboard popover. It is purpose-built for developers and power users who juggle multiple AI coding tool subscriptions and need at-a-glance visibility into their consumption patterns to avoid overage charges. Not intended for casual users or thos...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Native macOS menu bar tracker for AI coding subscription usage across eight providers
OpenUsage is a Swift-based macOS menu bar application that aggregates usage metrics for AI coding subscriptions (Claude, Cursor, Codex, Devin, Grok, OpenRouter, Z.ai, Antigravity). Launched February 2026, it has attracted 3,049 stars and 118 stars in the past week, positioning it as a competitor in a narrow but active ecosystem of similar trackers. The project solves a specific pain point: developers paying for multiple AI coding services need visibility into their consumption without context-switching between vendor dashboards. Adoption appears concentrated among macOS users with multi-subscription workflows.
OpenUsage entered a crowded macOS menu bar tracker space in February 2026. Competitors like hamed-elfayome/Claude-Usage-Tracker (2,854 stars), tddworks/ClaudeBar (1,274 stars), and nguyenphutrong/quotio (4,493 stars) preceded it. The project differentiates by native Swift architecture, support for eight providers, and credential-reuse from local stores rather than mandatory API key entry for most services.
The project gained 118 stars in the past 7 days (relative to June 30, 2026), suggesting active discovery — likely driven by its positioning as a multi-provider aggregator versus single-service trackers. The rapid climb from February launch to 3,049 stars in ~5 months indicates strong appeal within the macOS developer community, though the similar-repos list shows this is a fragmented category where multiple players coexist rather than one dominant winner. Growth rate appears healthy but not explosive relative to category leaders like quotio (4,493 stars).
Adoption not verified through public data. No case studies, company testimonials, or explicit deployment counts are provided. GitHub stars (3,049) and weekly growth suggest user interest, but real-world retention and active usage cannot be confirmed. The existence of a local HTTP API for inter-app communication suggests intended integration scenarios, but adoption of this capability is not documented.
Likely a SwiftPM executable using SwiftUI for UI composition hosted in an AppKit NSStatusItem and NSPopover. README explicitly mentions Swift 6 strict concurrency, which suggests adherence to modern Swift practices. Providers implement a ProviderRuntime protocol pattern for abstraction. Local HTTP API (127.0.0.1:6736) exposes usage as JSON for other applications. Architecture appears sound for a specialized menu bar utility, though actual code quality cannot be assessed from README alone.
Not documented in README. README mentions `swift test` command, implying a test suite exists, but no coverage metrics, test count, or testing strategy are disclosed.
Last push on June 29, 2026 (1 day before analysis date) indicates active ongoing development. Created February 1, 2026 (~5 months old). Releases are automated via GitHub Actions with semantic versioning and early-access beta channel. Documentation is comprehensive (architecture, provider setup, local API, proxy support, debugging guide). High update frequency and maintenance activity suggest the maintainer is actively developing and responding to the ecosystem.
ADOPT IF: you are a macOS user managing multiple AI coding subscriptions (Claude, Cursor, Codex, Devin, etc.) and want unified menu bar visibility without manual logins for most services; the app is actively maintained, well-documented, and supports credential reuse from local stores. AVOID IF: you need cross-platform support (Windows, Linux), use only a single AI service, or are risk-averse with brand-new projects (<6 months old). MONITOR IF: you rely on the local HTTP API for integration with other tools — adoption of this feature is unclear, and API stability guarantees are not documented.
Independent dimensions
Mainstream potential
3/10
Technical importance
4/10
Adoption evidence
2/10
- Highly dependent on macOS ecosystem — limits addressable market and requires ongoing maintenance with Apple SDK changes.
- Very new project (5 months old) — unknown long-term maintainability, API stability, or breaking-change frequency.
- Fragmented category with multiple competing trackers — no clear winner; risk of category stagnation if user switching costs are low.
- Credential handling and security posture not documented in README — users cannot independently assess whether local storage and API proxying are secure.
- Provider-specific parsing likely brittle — any vendor API or UI change could break usage extraction; no documented strategy for monitoring/alerting on provider changes.
OpenUsage likely remains a viable niche tool for multi-subscription macOS users over the next 12–24 months, assuming maintainer commitment holds. Risk of declining relevance if consolidation occurs (e.g., unified AI billing platforms emerge, or a vendor integrates all trackers). Probability of becoming a dominant category leader is low — the problem space is narrow and lacks strong competitive moat.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://www.openusage.ai
- Language
- Swift
- License
- MIT
- Last updated
- 8h ago
- Created
- 5mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Top contributors
Similar repos
hamed-elfayome/Claude-Usage-Tracker
Claude Usage Tracker is a native macOS menu bar application that monitors...
tddworks/ClaudeBar
ClaudeBar is a macOS menu bar application that monitors API usage quotas across...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
robinebers/openusage
this
|
3.2k | +112 | Swift | 8/10 | 8h ago |
 steipete/CodexBar
|
17.4k | — | Swift | 8/10 | 8h ago |
|
hamed-elfayome/Claude-Usage-Tracker
|
3k | — | Swift | 8/10 | 3mo ago |
 nguyenphutrong/quotio
|
4.5k | — | Swift | 7/10 | 9h ago |
|
tddworks/ClaudeBar
|
1.3k | — | Swift | 7/10 | 1w ago |
 Maciek-roboblog/Claude-Code-Usage-Monitor
|
8.4k | — | Python | 8/10 | 5d ago |
Similar positioning (Claude-focused tracker). OpenUsage is newer but covers 8 providers; Claude-Usage-Tracker appears single-vendor. OpenUsage has 3,049 vs. 2,854 stars despite later launch, suggesting broader appeal of multi-provider approach.
4,493 stars, likely the category leader in this niche. OpenUsage trails by ~1,400 stars but has momentum (118/week). Quotio's specific positioning and provider support not documented in this analysis; unknown whether differentiation is real or marginal.
1,274 stars, single-service tracker. OpenUsage's multi-provider design is a clear functional advantage for users managing multiple subscriptions.
15,525 stars but language is Swift (same as OpenUsage), suggesting it may be a different category or older established project. Unknown if directly comparable.
8,301 stars, Python-based, likely cross-platform or web-based. OpenUsage's native Swift/macOS focus is a trade-off: simpler native experience but platform-limited.
