Weekly quota incorrectly exhausted — Go subscription (started Aug 18), only ~$11 spent this cycle #43424

Activity

1. github-actions

   assigned

   MrMushrooooom

   on Aug 19, 2026
2. github-actions commented on Aug 19, 2026

   

   github-actionsBot

   on Aug 19, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Go quota shows 100% exhausted but visible usage is only ~$20 #38936: Go quota shows 100% exhausted but visible usage is only ~$20 (same symptom: weekly quota at 100% while dashboard spend is far below the limit)
   • OpenCode Go weekly/monthly quota does not match usage history #41206: OpenCode Go weekly/monthly quota does not match usage history (same issue: ~$11 spend shows 100% weekly quota)
   • The usage-based billing doesn't match the total subscription usage #43416: The usage-based billing doesn't match the total subscription usage (recent subscriber, similar mismatch between spend and quota percentage)
   • Go quota accounting does not match Usage History or documented limits #41391: Go quota accounting does not match Usage History or documented limits
   • OpenCode Go quota usage inconsistency: Monthly usage percentage exceeds Weekly usage percentage with mismatched cost statistics #43023: OpenCode Go quota usage inconsistency: Monthly usage percentage exceeds Weekly usage percentage with mismatched cost statistics

   These all describe the same underlying problem: the quota percentage shown does not match the visible USD spend in the usage history. You may want to follow or add a reaction to one of those issues rather than opening a new one.
3. Zaczero commented on Aug 19, 2026

   

   Zaczero

   on Aug 19, 2026

   More actions

   Weekly 100% and monthly 50% are the same $30 of quota-dollars. Usage History ~$11 is before the model factor.

   bar	shown	window	dollars
   rolling	50%	$12	$6 still in the 5-hour window
   weekly	100%	$30	$30
   monthly	50%	$60	$30

   Quota is visible × (60 / Usage). Usage is the last column at https://opencode.ai/docs/go/#usage-limits.

   The chart is mostly Grok 4.5, GLM-5.3, GPT-5.6 Luna, Kimi K3, Qwen3.8 Max — all Usage $15 → 4× — plus GLM-5.2 / MiniMax M3 (Usage $60 → 1×). $11 of that mix is $30 of quota, which is the weekly cap. $11 / $30 = 37% is what weekly would show if the bars read Usage History directly.
4. admaxistrator commented on Aug 19, 2026

   

   admaxistrator

   on Aug 19, 2026

   Last edited by admaxistrator

   More actions

   I have the same issue:

   • The meter's reset timer shows the weekly window is Mon Aug 17 00:00 UTC → Mon Aug 24 00:00 UTC.
   • Usage history for that exact window: 2,041 requests (deepseek-v4-flash + glm-5.3) = $11.71, while the meter shows 100% of the $30 limit – 2.5x over. I re-priced every record against the official rate card (including peak hours) and the history adds up exactly, so it's not under-billed.

   

   EDIT:

   Zaczero's formula reproduces my numbers almost exactly: my week is $8.18 deepseek-v4-flash (×2) + $3.52 glm-5.3 (×4) = $30.46 quota-dollars → exactly the $30 weekly cap.

   If that per-model weighting is intended, it isn't documented anywhere. The Usage page shows flat $ and the meter counts a different $.
   The ask becomes: document the formula, and make the bars show quota-$ vs list-$ so users can predict when they'll hit the cap.
5. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
6. thdxr

   closed this as not plannedon Oct 11, 2026