AI coding usage tracker for the macOS menu bar
Monitor quotas, reset windows, billing renewals, and pace for Codex, Cursor, Devin, and OpenCode Go.
LimitLens is a native macOS menu bar app (no Dock icon) that aggregates usage from multiple AI coding assistants into one color-coded popover. It fetches on a configurable interval and shows live progress rings, countdowns, renewals, and diagnostics in the menu bar.
Design principles
- Runs entirely locally — no accounts, cloud sync, or telemetry
- Native Swift / SwiftUI — not Electron
- Privacy-first — provider names can be hidden in the UI and menu bar
- Zero-config start — auto-detects installed providers on first launch
| Provider | What it tracks |
|---|---|
| Codex (OpenAI) | Primary/secondary rate limits, reset credits, token usage, API-equivalent cost, daily streaks |
| Cursor | Plan $ usage, Auto/API sub-limits, billing cycle, plan type |
| Devin (Windsurf) | Daily & weekly quotas, overage balance, plan cycle |
| OpenCode Go | Rolling / weekly / monthly windows, billing balance, payment history |
Each provider can be enabled or disabled independently. Disabled providers are not fetched and do not appear in the overview or menu bar.
- Multi-provider overview with severity coloring
- Live menu bar progress rings and countdown pills
- Billing / renewal tracking with urgency colors
- Pace projection (“will exhaust before reset” vs spare capacity)
- Codex and Cursor burn-down charts with target, actual, current, and historical pace
- Rolling Codex usage and API-equivalent cost for the last 24 hours, 7 days, and 30 days
- Exhaustion history with average time-to-exhaust
- Per-provider detail tabs, diagnostics, and on-demand refresh
Six popover layouts, switchable in Settings → Appearance:
| Theme | Layout |
|---|---|
| Classic | Balanced cards with top tab navigation |
| Studio | Spacious workspace with a labeled sidebar |
| Terminal | Compact dark console look with monospaced UI |
| Pulse | Meter-first cards with bottom navigation |
| Harbor | Teal instrument panel with segmented navigation |
| Constellation | Orbital signal map with a connected node spine |
Configurable from Settings (or the footer toggle):
- Logos — progress rings with provider icons
- Countdowns — compact time-remaining pills
- Auto — alternates logos and countdowns
- Hidden — anonymizes providers to “Provider 1–4” and uses generic glyphs
Failed fetches with cached data show a stale indicator.
Native macOS notifications (local only):
| Notification | Trigger |
|---|---|
| Critical usage | Crosses threshold (default 90%, per-provider override) |
| Billing expiring | Renewal within 7 days |
| Provider unavailable | Fetch failure |
| Daily digest | Once per day at a configured hour |
Also supports quiet hours, per-provider toggles, and a test notification button. Notifications require running from the .app bundle (not swift run).
- Intervals: 1 / 3 / 5 / 15 / 30 min, or custom 1–60
- Retry with configurable max attempts
- Parallel provider fetches; per-provider refresh
- Clears stuck refresh state after sleep/wake
- macOS 13 (Ventura) or later
- Xcode 15+ or a Swift 6.0 toolchain
git clone https://github.com/sebbonit/LimitLens.git
cd LimitLens
swift run LimitLensLook for the LimitLens icon in the menu bar.
Scripts/build-app.sh
open .build/LimitLens.appThis creates a standalone .app you can move to Applications. Prefer the .app for notifications and reliable URL opens.
On first launch, LimitLens enables only providers with detected paths. Adjust everything in the Settings tab.
Config file
~/Library/Application Support/LimitLens/config.json
Corrupt configs are renamed to config.invalid.json and defaults are loaded.
OpenCode Go usage is scraped from the web dashboard (the CLI token does not expose usage windows). On first launch, Settings opens with a dashboard auth form.
You need:
- Workspace ID from a URL like
https://opencode.ai/workspace/<workspace-id>/go - Browser cookie named
authforopencode.ai
The form writes ~/.config/opencode/opencode-quota/opencode-go.json. For a terminal fallback:
Scripts/configure-opencode-go.shSee RUNBOOK.md for more local-run details.
| Module | Type | Role |
|---|---|---|
LimitLens | Executable | SwiftUI app, menu bar, settings, notifications, config store |
LimitLensCore | Library | Provider clients, models, formatting, pace & exhaustion math |
UsageViewModel.start()
├─ Refresh loop (parallel provider fetches)
│ ├─ Codex (app-server JSON-RPC + chatgpt.com APIs)
│ ├─ Cursor (SQLite auth → api2.cursor.sh)
│ ├─ Devin (protobuf / local language server / SQLite)
│ └─ OpenCode Go (dashboard HTML scrape)
├─ Notification coordinator
└─ Clock loop (1 min) → live countdowns
swift build # debug
swift build -c release # release
swift build -c release --show-bin-path
swift test
swift run LimitLensLimitLens/
├── Package.swift
├── Sources/
│ ├── LimitLens/ # App UI, view model, config, notifications
│ └── LimitLensCore/ # Provider clients and shared logic
├── Tests/
│ ├── LimitLensTests/ # App / config / menu bar / notifications
│ └── LimitLensCoreTests/ # Parsing, fixtures, pace, exhaustion
├── Resources/ # Info.plist, icons
├── Scripts/ # build-app.sh, configure-opencode-go.sh
├── docs/screenshots/
├── AGENTS.md
├── RUNBOOK.md
└── README.md
Coding guidelines for contributors and agents live in AGENTS.md.
swift test203 tests across core parsing, pace projection, quota history, menu bar status, notifications, configuration, refresh, exhaustion history, diagnostics, and dashboard links.
When changing JSON/HTML parsing, add fixtures under Tests/LimitLensCoreTests/Fixtures/.
Does LimitLens send data to its own servers?
No. It talks only to the provider APIs/dashboards you already use, with credentials already on your Mac.
Does it store passwords or tokens?
It reads existing auth (e.g. ~/.codex/auth.json, Cursor’s SQLite DB, OpenCode Go cookie config). App settings are saved under Application Support; do not commit those files.
Why does OpenCode Go need a cookie?
The CLI token does not expose usage windows. Dashboard scraping needs the auth cookie, stored locally and sent only to opencode.ai.
Can I hide provider names for screenshots?
Yes — use Hidden menu bar display mode in Settings.
Notifications or “Open dashboard” do nothing under swift run?
Use the .app from Scripts/build-app.sh. Menu bar agent processes started via SwiftPM are limited for notifications and some Launch Services URL opens.
Pull requests are welcome. Keep commits focused, add tests for new behavior, and run swift test before opening a PR.
- Add an async client in
Sources/LimitLensCore/with fixtures inTests/LimitLensCoreTests/Fixtures/ - Add a
ProviderTabcase and section view inSources/LimitLens/ - Wire refresh, overview summary, menu bar, and notifications
- Cover with tests in both test targets
MIT