OpenCode: Go quota, tokens and replies
Agent HUD reads OpenCode's sessions and tokens, shows the OpenCode Go plan's limits, and tells you when OpenCode replies.
Updated 2026-10-26
At a glance
| Feature | OpenCode |
|---|---|
| Tokens and sessions | ✓ |
| Quota | ✓ |
| Live status | — |
| Approvals | — |
| Questions | — |
| Replies | ✓ |
| One click back | ✓ |
| Turns and calls | — |
What you see on the HUD
With an OpenCode Go plan, the glow and the hover show its five-hour, weekly and monthly limits, each with its reset, beside OpenCode's sessions. A Kimi Code plan or a GLM Coding Plan whose key OpenCode holds shows its own limits too; see Kimi and GLM Coding Plan. Requests paid by the token have no limit to show; their tokens still count.
Which account does it count against?
The OpenCode Go plan behind the key OpenCode already holds, in its settings, its sign-in file or the environment. Agent HUD asks OpenCode Go's own usage service with that key; it signs in to nothing and refreshes no token.
Running turns and replies
Agent HUD does not show OpenCode working during a turn. Agent HUD's OpenCode plugin records each turn when it completes, which brings a New reply reminder. When OpenCode runs in iTerm outside tmux, one click takes you back to its pane.
The release adds the plugin to OpenCode's plugin folder while client hooks are on and removes it when they are off. Approvals and questions stay in OpenCode.
What does Agent HUD read?
OpenCode's database and message store, for tokens and sessions, and the plan entries in its settings for the quota. No message goes to a model.
On iPhone and Apple Watch
On the same network as the release, iPhone and Apple Watch show OpenCode's quota, tokens and sessions without a subscription. Agent HUD Remote shows them on any network.