anomalyco / anomalyco/opencode
Go: 5-hour usage limit blocks all models after one model hits its own limit
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Summary
After grok-4.6 hit its own 5-hour usage limit, every other OpenCode Go model
with zero usage started returning the same "5-hour usage limit reached" error,
with the same rolling reset window. Switching models does not help.
Environment
- opencode 1.18.30
- OS: Windows (win32)
- Provider: opencode-go
- Workspace: wrk_01M253ZBQ65WYRCXEEQE0SVV17
Expected
Per docs (https://opencode.ai/docs/go/), usage limits are per-model
(5h = 20% of that model's monthly limit). GLM-5.3, DeepSeek, Kimi etc. had
zero usage, so they should remain usable.
Actual
grok-4.6 is the only model with spend ($3.17, its 5h cap is $3.00) — legitimately
blocked. But all other models return the identical error with the same countdown,
across separate sessions and even for tiny title-generation requests.
Console usage page shows grok-4.6 only; every other model = $0.
Steps to reproduce
- Use grok-4.6 until its 5h limit is reached.
- Switch to glm-5.3 / deepseek-v4.1-flash / kimi-k3 (all $0 usage).
- Send any request (new session, minimal prompt).
- Same error: "5-hour usage limit reached. Resets in X".
Log evidence (opencode.log, 2026-09-14)
Different models, same error and same rolling reset window:
- 15:49 grok-4.6 (subagent)
- 16:16 muse-spark-1.2-contributor
- 16:17 / 16:25 glm-5.3
- 16:21 deepseek-v4.1-flash
- 16:31 kimi-k3 (new session) + title generation
Attached: log excerpts + console screenshot.
Impact
Paid models unusable for the remainder of the window, despite per-model
allowances by design.
Plugins
No response
OpenCode version
1.18.30
Steps to reproduce
No response
Screenshot and/or share link
<img width="1192" height="722" alt="
Image" src="https://github.com/user-attachments/assets/1a4ea3fb-58d8-42ec-81b8-e1bce89b52f1" />
Operating System
Windows 11
Terminal
OpenCode
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.
Research direction
Start with the opencode-go provider path and the usage-limit behavior described in the issue. Compare requests for grok-4.6 with zero-usage models using the attached opencode.log evidence and console usage page. Done means one model reaching its 5-hour limit no longer blocks other models with unused allowances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100