Home / Guides / Best opencode Trackers
Best opencode Usage Trackers for macOS (2026)
opencode is bring-your-own-key, so “how much have I used” is really your provider's usage — spread across Anthropic, OpenAI, or OpenRouter. Here are the four real ways to track your opencode tokens, cost, and the underlying rate-limit window, ranked.
Last updated June 2026 · For sst/opencode · By Soren Starck
Why You Need a Usage Tracker for opencode
If you use opencode daily, you know the pattern: you're deep in a reasoning-heavy session, the agent is iterating, and then requests start failing. You hit the provider's rate limit or spend cap — with no warning it was coming.
The catch unique to opencode is that the limit isn't opencode's — it's whichever provider you routed to. Point opencode at a Claude subscription and you inherit Anthropic's rolling 5-hour and weekly windows; use a raw API key and you inherit per-key rate limits and per-token cost; use OpenRouter and you inherit its credits and limits. The built-in footer shows this session's spend and nothing about where you stand against any of those.
A usage tracker fixes this by giving you visibility before the lockout, and by stitching the providers together so you're not reconciling three dashboards. We tested four approaches. Here's how they compare.
#1: SessionWatcher for opencode Editor's Pick
SessionWatcher for opencode is a native macOS menu bar app built specifically for tracking opencode. It reads opencode's local session logs, detects which provider each request used, and updates in real time as the agent burns tokens — without ever touching your API key.
What it tracks:
- Provider auto-detection: Anthropic, OpenAI, or OpenRouter — it knows which one opencode is burning right now.
- Underlying rate-limit window: the active provider's 5-hour / weekly / monthly window, surfaced live.
- Per-model tokens & cost: aggregated across sessions, so it doesn't reset every time you restart opencode.
- Dollar cost: what today is actually costing you, translated for you.
- Rate-limit percentage: a single number in your menu bar: “67% used.”
- macOS notifications: configurable thresholds so you can pivot before getting cut off.
Setup: Download, drag to Applications, paste your license key. Tracking in under 30 seconds. No API keys, no scripts.
Pricing: Part of Pro — $49 one-time (or $24/year) — covering all 7 tools.
Limitations: macOS only (requires macOS 15+).
#2: The opencode Session Footer
opencode prints the running token count and session cost in its TUI status line as the agent works. It's the fastest free signal for “what is this conversation costing me.”
What it shows:
- Tokens consumed in the current session
- Running dollar cost for the current session
Pricing: Free (built into opencode).
Limitations: per-session only — it resets when you start a new session and never aggregates your day or week. It shows spend, not remaining budget, and knows nothing about the provider's rate-limit window. No notifications, and it's gone the moment you switch out of the terminal.
#3: Provider Usage Dashboards
The official source for historical totals is whichever provider opencode is configured to use: Anthropic Console, platform.openai.com/usage, or openrouter.ai/activity.
What they show:
- Historical tokens and spend by model
- Per-request cost (especially clear on OpenRouter)
- Account-level limits and remaining credits
Pricing: Free.
Limitations: data lags by minutes, lives in a separate browser tab, and lumps opencode in with everything else hitting that key — no “this was opencode” filter. Route across two providers and you're reconciling two dashboards by hand. None show your live position in a rolling window.
SessionWatcherStop reconciling three dashboards.
Just glance up.
Native macOS menu bar app. Track Claude and Codex usage, costs, and rate limits in real-time.
“Fast, simple, and does exactly what it should. Definitely worth it.”
@nicojerome on GitHub
macOS 14+. 7-day Bundle trial. No credit card.
#4: DIY Scripts (provider APIs + cron)
Some developers build their own monitoring by polling each provider's usage API on a schedule, parsing opencode's session files, or wrapping the CLI to log tokens locally.
Typical approaches:
- Scripts that hit the Anthropic / OpenAI / OpenRouter usage APIs on a cron schedule
- Parsers over opencode's local session data to sum tokens and cost
- SwiftBar / tmux plugins that re-print the latest totals on an interval
- A custom dashboard stitching all three providers together
Pricing: Free, plus your time.
Limitations: the usage APIs lag, which defeats real-time lockout avoidance. opencode's session format and provider routing change across releases — your parser will break. Rolling-window math has to be reimplemented per provider. Most developers ship a v1 in a weekend, then abandon it after two breakages.
A note on ccusage and Claude-Code-Usage-Monitor
If you searched for “opencode usage tracker” and ran into these tools, they're Claude-only. ccusage, Claude-Code-Usage-Monitor, and Claude Usage Tracker all read Anthropic's local ~/.claude/projects/*.jsonl files. opencode stores sessions differently and often routes to OpenAI or OpenRouter. For opencode you need a provider-aware tool.
Comparison: All 4 Options at a Glance
| Feature | SessionWatcher | Footer | Dashboards | DIY |
|---|---|---|---|---|
| Provider auto-detect | Yes | Manual | One per tab | Hard to build |
| Live rate-limit window | Yes | No | No | Hard to build |
| Aggregates across sessions | Yes | No (resets) | Lagged | Manual |
| macOS notifications | Yes | No | No | DIY |
| Dollar cost | Yes | Session only | Yes | Varies |
| No workflow interrupt | Menu bar | In terminal | Browser tab | Varies |
| Setup time | 30 seconds | None | None | Hours+ |
| Price | Pro $49 once | Free | Free | Free + time |
The Verdict
For developers on macOS who use opencode daily, SessionWatcher for opencode is the only option that gives you the full picture: which provider is being burned, the underlying rate-limit window, per-model tokens and cost aggregated across sessions, and notifications — without making you stop coding.
The free options work if opencode is occasional for you. But if it's part of your daily workflow and a single mid-session lockout costs an hour of momentum, a one-time Pro license pays for itself the first time.
SessionWatcherThe opencode tracker that's actually always on.
Part of Pro. One-time.
Native macOS menu bar app. Track Claude and Codex usage, costs, and rate limits in real-time.
“Fast, simple, and does exactly what it should. Definitely worth it.”
@nicojerome on GitHub
macOS 14+. 7-day Bundle trial. No credit card.
Frequently Asked Questions
What is the best opencode usage tracker for Mac?
SessionWatcher for opencode is the best dedicated tracker. Live in your menu bar, it auto-detects the provider, surfaces the rate-limit window, aggregates tokens and cost across sessions, and notifies you before lockout.
Can I track opencode usage for free?
Yes — opencode's session footer is free, and the Anthropic, OpenAI, and OpenRouter dashboards are free for historical data. Neither is real-time, provider-aggregated, or always-visible.
Do free Claude trackers like ccusage work with opencode?
No. ccusage and similar tools read Claude Code session files only. They don't parse opencode sessions or non-Anthropic providers. See our how to check opencode usage guide for the full set of options.
How much does SessionWatcher for opencode cost?
opencode tracking is part of Pro — $49 one-time (or $24/year) — covering all 7 tools.