anomalyco / anomalyco/opencode
Zen balance available but OpenCode says "Free usage exceeded, subscribe to Go"
@fwang is already working on this.
Since Aug 26, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
I added $10 in credits to my OpenCode Zen account.
My Zen dashboard currently shows an available balance of $9.99, so there are sufficient paid credits available.
However, OpenCode stops processing requests and displays:
Free usage exceeded, subscribe to Go [retrying in ...]
This is confusing because I already have paid Zen credits available.
Current behavior
Add $10 of credit to OpenCode Zen.
Zen dashboard confirms an available balance of $9.99.
Use OpenCode with a Zen free model such as Big Pickle.
After reaching the free usage limit, OpenCode displays:
Free usage exceeded, subscribe to Go
The existing Zen balance is not offered as an alternative and the error implies that purchasing a Go subscription is required.
Expected behavior
When a user has an available Zen balance, OpenCode should either:
allow the user to continue through the paid Zen endpoint/balance;
offer to switch from the free model to its paid Zen equivalent when available; or
clearly explain that the free-model quota is separate from the Zen prepaid balance and that the user must select a paid Zen model.
The current message makes it appear that the $9.99 Zen balance cannot be used and that subscribing to Go is the only way to continue.
Additional information
The Zen dashboard clearly shows:
Current balance: $9.99
I can provide the screenshot showing the available balance and the OpenCode error.
This appears related to previous reports involving free-model quotas and Zen/Go provider routing.
Plugins
No response
OpenCode version
No response
Steps to reproduce
- pay
- try to use, but can't
Screenshot and/or share link
No response
Operating System
windows 11
Terminal
windows terminal
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.