anomalyco / anomalyco/opencode
Weekly usage limit reported as exhausted while rolling 5h limit never reached
Open
@fwang is already working on this.
Since Jul 25, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Bug Report
Problem
My opencode-go subscription shows the rolling 5h limit is never exhausted, but I am told the weekly limit has been reached — reportedly twice. The limits should be independent; hitting the weekly cap without ever hitting the rolling cap is unexpected given typical usage patterns.
Reproduction steps
- Use OpenCode Go normally throughout the week
- Observe rolling 5h usage never maxes out
- Get told weekly limit is exhausted (reported twice in one week)
- No usage activity on the dashboard for the period affected
Expected behavior
The rolling 5h ($12/5h) and weekly ($30/week) limits should track independently. If the rolling 5h is never maxed, the weekly tracking should accurately reflect actual spend.
Observed behavior
- Rolling 5h usage: never reaches 100%
- Weekly usage: reported as exhausted twice within a week
- No activity shown on dashboard for affected periods
Environment
- OpenCode Go subscription
- Usage across various models
References
Existing related issues:
- #24473: quota persists after 2+ days of inactivity
- #15128: CLI not reading Go subscription quotas correctly
- #38570: Limit calculation bug (47% consumed but only $1.50 used)
- #26213: Go API returns cost "0" and dashboard not tracking usage
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.