Repository navigation
Go free models documented as "Unlimited" are blocked when any Go usage cap is reached #51682
Description
When a Go usage limit is reached (5h, weekly, or monthly), the block applies to the entire opencode-go provider. This includes the free models that are documented as Unlimited.
The Go docs list Space Bunny Free and LongCat 2.5 Preview Free with a monthly limit of Unlimited (limited time). These models have no dollar cap and should not be subject to any usage limit. However, when any Go model's cap is hit, requests to these free models are blocked with the same "5 hour usage limit reached" error.
Expected behavior
Free models on Go remain usable when paid-model caps are reached, since they carry no dollar limit. The block should apply only to the specific model whose cap was hit.
Actual behavior
All Go models, including free ones, become unusable. The only workaround is switching to the Zen provider and using free models there, which defeats the purpose of the Go subscription.
Steps to reproduce
- Subscribe to OpenCode Go
- Use any Go model until a usage limit is reached (5h, weekly, or monthly)
- Attempt to use
opencode-go/space-bunny-freeoropencode-go/longcat-2.5-preview-free - Observe the same "5 hour usage limit reached" error
Environment
- OpenCode version: 1.18.31
- OS: macOS
- Terminal: macOS Terminal
Related issues
- Go plan hits 100%, blocks 12h — "Use balance" enabled but $39.89 Zen balance never used, on any model #42938: "Use balance" enabled but Zen balance never drawn when Go cap is reached
- Free usage exceeded and there's long retry timers keep escalating across different free models #50093: Retry timers escalate across free models instead of counting down
- Go subscription active but still "Free usage exceeded" — paid, no access #36265: Go subscription active but all models blocked
Activity
github-actions commentedon Sep 27, 2026
This issue might be a duplicate of existing issues. Please check:
khaosdoctor commentedon Sep 27, 2026
Slightly different thing, it includes all the other issues
CinematicEnciclopedia commentedon Sep 28, 2026
Confirming from #42938: when my Go quota hit 100%, all models on the Go provider were blocked (~12h), so it looks like the same provider-wide lock you describe here.
For context: OpenCode Support told me by email (30/08) that the block I hit came from a separate account-level monthly usage limit, which "Use balance" does not override. That explains why the Zen balance isn't drawn, but not why models documented as Unlimited are locked as well. Agree that the lock should apply per model (or at least leave the free ones out), and that the error should say which limit was reached.
Cross-referencing so both get triaged together: #42938
shimpeiws commentedon Oct 2, 2026
I encountered a similar issue and found an additional workaround:
So, in my case, enabling Extra Usage allowed the free model to work again without switching to the Zen provider.
I haven’t verified whether the successful free-model requests deducted any credits. However, this suggests that access to free models may also depend on the Extra Usage setting once the Go quota is exhausted.
chrisssp commentedon Oct 6, 2026
I am experiencing this exact issue. I have the Go plan ($10/month) with 43% of the monthly limit remaining, and my 5-hour and weekly limits are at $0 (completely unused), yet I get "Go usage limit exceeded" on all models — including free models like mimo-v2.6-flash-free, ling-3.1-flash-free, and big-pickle.
The logs show mixed errors: "Go usage limit exceeded", "ECONNRESET", "Endpoint is unavailable", and "Rate limit exceeded", all in bursts of ~13 minutes.
My config uses
opencode-go/mimo-v2.5for build/plan/general andopencode-go/deepseek-v4.1-flashfor explore. If one model's 5-hour limit blocks all others, this makes the plan unusable for real work.Please prioritize the fix — the docs promise per-model limits but the implementation blocks the entire account. Thanks.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊