Home / Guides / opencode Usage
How to Check Your opencode Usage and Rate Limits
You can check opencode usage three ways: read the token count and running cost opencode prints in its status line for the current session, open the usage dashboard for whichever provider you've wired up (Anthropic, OpenAI, or OpenRouter), or use a menu-bar tracker for always-on, provider-aware monitoring without leaving your editor.
Last updated June 2026 · For sst/opencode, the open-source terminal coding agent · By Soren Starck, indie dev in Lyon and maker of SessionWatcher
Understanding opencode Usage Limits
There are two things you actually care about: cost (how many dollars this session is burning) and rate limits (when the provider stops you). Both live with the provider, not with opencode. If you point opencode at a Claude Pro/Max subscription you inherit Anthropic's rolling 5-hour and weekly windows; if you use a raw API key you inherit per-key rate limits and pay per token; with OpenRouter you inherit that provider's credits and limits.
The problem? opencode shows what you spent this session, but there's no built-in view of where you stand against the provider's limit, and no warning before you hit it. You're mid-refactor, the agent is iterating, and suddenly requests start failing with a rate-limit error.
Method 1: The opencode session footer
The fastest free check is built in. As the agent works, opencode prints the running token count and session cost in its TUI status line, so you can see what the current conversation is costing in near real time.
Limitations: it's per session. Start a new session and the counter resets, so it never aggregates your day or week. It shows what you spent, not what you have left, and it knows nothing about the provider's rolling rate-limit window. It also lives in the terminal you're actively typing in, so it's gone the moment you switch context.
Method 2: Your provider's usage dashboard
For historical totals, go to the dashboard of whichever provider opencode is configured to use:
- Anthropic: console.anthropic.com usage, or your Claude plan's limits if you're on a subscription.
- OpenAI: platform.openai.com/usage for tokens and spend by model.
- OpenRouter: openrouter.ai/activity for per-request credits and cost.
Limitations: the data lags by minutes, lives in a separate browser tab, and lumps opencode in with every other tool hitting that key — there's no “this was opencode” filter. If you route opencode across more than one provider, you're reconciling two or three dashboards by hand. None of them show your live position in a rolling window.
Method 3: Free CLI trackers (ccusage, etc.), and why they don't fit opencode
You may have seen open-source trackers like ccusage, Claude-Code-Usage-Monitor, or Claude Usage Tracker. They're good tools — for Claude Code specifically.
They all read Anthropic Claude Code's local ~/.claude/projects/*.jsonl session files. opencode stores its own session data and, critically, often routes to OpenAI or OpenRouter rather than Anthropic — so a Claude-only parser either sees nothing or attributes the wrong provider. To track opencode you need a tool that reads opencode's sessions and is aware of which provider each request went to.
Method 4: SessionWatcher (always-on, provider-aware, in your menu bar)
Here's the friction the free options share: the session footer is per-session and disappears, and the dashboards are laggy, fragmented across providers, and can't isolate opencode. None of them warn you before the provider cuts you off.
SessionWatcher for opencode is a native macOS menu bar app that reads opencode's local session logs, detects which provider each request used, and surfaces the picture you actually want — live, without leaving your editor. It never needs your API key.
- Provider auto-detection. See whether opencode is burning Anthropic, OpenAI, or OpenRouter right now.
- Underlying rate-limit window. The 5-hour / weekly / monthly window of the active provider, surfaced live.
- Per-model tokens & cost. Aggregated across sessions, not reset every time you restart.
- Dollar cost. What today is actually costing you, translated for you.
- macOS notifications. A heads-up before the provider locks you out, not after.
- 7 tools in one app. Claude Code, Codex, Cursor, Copilot, Gemini CLI, opencode, and Antigravity.
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.
Side-by-side: Session footer vs Provider dashboard vs ccusage vs SessionWatcher
| Capability | opencode footer | Provider dashboard | ccusage (CLI) | SessionWatcher |
|---|---|---|---|---|
| Reads opencode sessions | Yes | No | No (Claude only) | Yes |
| Provider auto-detect | Manual | One per tab | N/A | Automatic |
| Live rate-limit window | No | No | N/A | Always visible |
| Aggregates across sessions | No (resets) | Yes (lagged) | N/A | Yes (live) |
| Pre-lockout warning | None | None | N/A | macOS notification |
| Setup | Built in | Login each time | npm + CLI | 10-second install |
| Cost | Free | Free | Free | Pro $49 once |
Editorial note: ccusage is excellent for Claude Code. It doesn't read opencode sessions or non-Anthropic providers, which is why this page exists.
Frequently Asked Questions
How do I check my opencode usage?
Read the per-session token and cost line opencode prints in its status bar, open the usage dashboard for your configured provider (Anthropic, OpenAI, or OpenRouter) for historical totals, or use SessionWatcher for always-on, provider-aware monitoring.
Does opencode show how many tokens I have left?
No. opencode shows what the current session has consumed, not your remaining budget or your position in the provider's rolling window. Because opencode is bring-your-own-key, “remaining” depends on the provider it's routing to.
Why did opencode start erroring mid-session?
You most likely hit the rate limit or spend cap of the underlying provider, not a limit in opencode. SessionWatcher shows that provider's live usage in your menu bar and warns you before the cutoff.
Does ccusage work with opencode?
No. ccusage parses Claude Code's local JSONL files and is Claude-only. opencode stores its own sessions and often routes to OpenAI or OpenRouter, so Claude-only trackers can't attribute opencode usage. See our best opencode usage trackers roundup for the full comparison.
Is there an opencode usage tracker for macOS?
Yes. SessionWatcher for opencode is a native macOS menu bar app. It's part of Pro — $49 one-time (or $24/year) — covering all 7 tools. Zero configuration, never needs your API key.