anomalyco / anomalyco/opencode
Weekly usage quota stays maxed out (100%) even after the new monthly billing cycle starts, blocking usage despite ample monthly budget
@fwang is already working on this.
Since Sep 6, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Description
My subscription's monthly usage cycle renewed (new month started), and the monthly quota correctly reset to a fresh, mostly-unused state. However, the weekly quota is still showing 100% used (fully exhausted) from before the renewal, and is blocking me from using any models — even though I have plenty of monthly budget left. The weekly counter did not reset alongside the monthly one, and instead keeps counting down on its own separate schedule.
Observed data (screenshot, 2026-09-06)
- 5-hour usage: 0% (resets in 5h 0m)
- Weekly usage: 100% (resets in 11h 28m)
- Monthly usage: 10.4% (resets in 28 days 20h)
Weekly breakdown (100% total):
┌──────────────────────────────┬──────────────┬──────────────┬───────┐
│ Model │ Weekly Usage │ Weekly Quota │ % │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ DeepSeek V4 Pro │ $5.1922 │ $7.50 │ 69.2% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ DeepSeek V4 Flash │ $2.0342 │ $15.00 │ 13.6% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ GLM 5.3 Flash │ $1.4907 │ $15.00 │ 9.9% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ Muse Spark 1.3 Contributor │ $1.3907 │ $30.00 │ 4.6% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ Qwen3.7 Plus │ $0.7324 │ $30.00 │ 2.5% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ DeepSeek V4 Flash Vision Exp │ $0.0158 │ $7.50 │ 0.2% │
├──────────────────────────────┼──────────────┼──────────────┼───────┤
│ Total │ │ │ 100% │
└──────────────────────────────┴──────────────┴──────────────┴───────┘
Monthly breakdown (10.4% total):
┌──────────────────────────────┬───────────────┬───────────────┬───────┐
│ Model │ Monthly Usage │ Monthly Quota │ % │
├──────────────────────────────┼───────────────┼───────────────┼───────┤
│ DeepSeek V4 Flash │ $1.5609 │ $30.00 │ 5.2% │
├──────────────────────────────┼───────────────┼───────────────┼───────┤
│ GLM 5.3 Flash │ $0.9959 │ $30.00 │ 3.3% │
├──────────────────────────────┼───────────────┼───────────────┼───────┤
│ Muse Spark 1.3 Contributor │ $1.0794 │ $60.00 │ 1.8% │
├──────────────────────────────┼───────────────┼───────────────┼───────┤
│ DeepSeek V4 Flash Vision Exp │ $0.0158 │ $15.00 │ 0.1% │
├──────────────────────────────┼───────────────┼───────────────┼───────┤
│ Total │ │ │ 10.4% │
└──────────────────────────────┴───────────────┴───────────────┴───────┘
Note the monthly breakdown doesn't even include DeepSeek V4 Pro or Qwen3.7 Plus — consistent with the monthly cycle having freshly reset — while the weekly breakdown for those same models is still nearly/fully exhausted from the prior cycle.
Expected behavior
Either:
- The weekly quota should reset when the monthly billing cycle renews (if it's meant to be tied to the subscription cycle), or
- If weekly and monthly are intentionally independent rolling windows on different clocks, this should be clearly surfaced to the user — right now it's confusing/blocking to see 100% weekly usage with only 10.4% monthly usage, with no indication of why the weekly window didn't also refresh.
Actual behavior
After the monthly renewal, monthly usage correctly reset to a low, fresh value (10.4%), but weekly usage remained at 100% (maxed out) with its own independent 11h28m countdown, fully blocking usage despite abundant monthly budget remaining.
Environment
- opencode version: 1.18.29
- Provider/plan: opencode-go (paid tier)
- Date observed: 2026-09-06
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
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.