Go plan: $60/month quota exhausted in 6 days while the client recorded only $14.80 of usage — cache-read billing is invisible, undocumented, and the local cost meter is misleading users

Description

I am a paying Go plan subscriber ($10/mo). Within 6 days of my billing cycle (Aug 6 - Aug 12, 2026), both the dashboard and the opencode UI show my monthly quota ($60) as essentially exhausted - yet the usage recorded locally by the opencode client itself totals only $14.80. That is a 4x discrepancy between what the product tells me I am consuming and what is actually metered against my quota. I find this deeply misleading.

Reproduction steps

1. Subscribe to the Go plan.
2. Use opencode-go models (deepseek-v4-flash, kimi-k3) for 6 days - 1,791 assistant messages, 5.94M input / 778K output / 371M cache-read tokens (all recorded in the local opencode SQLite database).
3. Compare the locally recorded cost with the Go quota dashboard percentages.

Expected behavior

The local cost field should match what is metered against the Go quota, or the metered figure should be transparent (per-request billing breakdown, published cache-read pricing).

Actual behavior

• Local recorded cost: $14.80; dashboard: monthly quota essentially exhausted.
• deepseek-v4-flash alone accumulated 359M cache-read tokens, recorded locally at $0.00.
• No warning before exhaustion; no per-request breakdown available to reconcile the 4x difference.

Impact

I paid for a month of usage and received 6 days of paid models; the remaining ~24 days of my paid cycle are unusable unless I fall back to free models.

Additional context

Local data from the opencode SQLite database (every assistant message this cycle):

If cache reads are metered anywhere near full input price, true consumption lands around $40-$70 - consistent with an exhausted $60 cap. The official Go docs state only the three rolling windows ($12/5h, $30/week, $60/month) and say nothing about cache token pricing.

Related reports with the same symptom (visible usage far below exhausted quota):

• #38255 - ~$34 visible usage, monthly quota 100% blocked
• #41206 - ~$11 visible usage, weekly quota 100%
• #41391 - maintainer-opened question about Go quota accounting model

I paid for $60 of usage across a month. I got 6 days, with a meter that claimed I had spent a quarter of my quota while draining it entirely. Whether this is an accounting bug or intentional opacity, it needs an answer - I expect a written explanation, a per-request audit of my account, and compensation for the unusable remainder of my billing cycle.