OpenCode

OpenCode Go: how to check usage

Check usage on an OpenCode Go plan: what the local database shows, what the plan enforces, and where to look for remaining capacity.

Quick answer

OpenCode Go usage splits into two numbers: tokens recorded locally by the client, and the plan allowance enforced by OpenCode. The local database shows the first. The second is shown in your OpenCode account or the CLI where the plan is exposed. Local tracking cannot see remaining plan capacity on its own.

What local data shows

  • Tokens per session, model, and day.
  • Cost where the provider reports it.
  • Which projects consumed the most.
  • How usage changed after a plan change.

This is consumption, not allowance. It answers what you used, not what is left.

Where the plan limit lives

Plan limits belong to the account. Check the OpenCode account page or the CLI output that reports the plan. Reset behaviour depends on the plan terms, so read the current terms rather than a copied number.

QuestionSource
Tokens used todayLocal database
Cost of a sessionLocal database
Remaining plan capacityOpenCode account
Reset timeOpenCode account or plan terms

Combine the two

Use the local number to understand behaviour and the account number to know when to stop. UsageAtlas covers the first; a connected provider covers the second where supported.

Using a plan instead of keys

OpenCode works with provider keys, but you can also point it at a subscription-style provider that meters usage on its own side. When you do, the local database still records tokens, but the limit that blocks you lives in the provider's console.

  • Local tokens tell you what a task cost in model terms.
  • The provider tells you how much allowance remains.
  • The two numbers will not match exactly, because plans price access, not tokens.
  • Keep both visible to avoid guessing which one is the constraint.

The usage tracker guide covers setup, and multi-provider usage covers the mixed case.

Questions, answered

Is OpenCode Go the same as OpenCode?

OpenCode is the client; OpenCode Go is a subscription offering with its own allowance terms. Check the current plan page for what it includes.

Can UsageAtlas show my OpenCode Go balance?

It can track local tokens and cost. Remaining plan capacity requires the provider's own reporting.

Do local tokens count against the plan?

All usage through the plan does. Local files record the same sessions, which is why the two numbers usually track closely.

Browse by topic