Agent HUD · Guides · Supported clients
OpenCode and OpenCode Go usage on Mac
OpenCode itself keeps the logs; the quota belongs to whichever plan paid for the work.
At a glance
| Quota | Rolling 5 h, weekly, monthly per pool |
|---|---|
| Account | Billing pool |
| Balance or cost | Per-request cost from the log |
| Running · completion | No · No |
| Credentials read | Plan entries only |
What you see
For OpenCode Go, a rolling five-hour window, a weekly window and a monthly window per billing pool. Requests paid another way have no window and show a cost instead.
How the account is named
A billing pool rather than a personal account — who paid, independent of which program made the request. A configured base URL only counts as a plan when it is an official coding endpoint.
Running turns and completions
Neither running turns nor completions are detected.
What Agent HUD reads
The OpenCode database and message store, and the entries that say which plan is in use. A message present in both stores counts once.
Common questions
- Why does plain OpenCode show no quota?
- Only the Go plan exposes windows. Requests billed another way still have their tokens and their cost read from the log, and those appear as usage rather than as a percentage.
- What is a billing pool?
- It identifies who pays, independently of the program that made the request, so the same plan used from OpenCode and from Pi is one set of windows rather than two. Windows of one pool are never added together.
Last updated: 2026-09-20 · The behaviour described here is documented in full, with the code it comes from, in Agent HUD Open. providers.md