anomalyco / anomalyco/opencode
Go: usage log totals $3.31 but the 5-hour limit reported $12 (factor 3.6)
@MrMushrooooom is already working on this.
Since Aug 23, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Summary
On August 23, 2026 my OpenCode Go session was cut off by the 5-hour usage limit. My own Usage History page, added up row by row for that entire window, totals $3.31 — but every meter on the subscription page reports $12.00.
That is a factor of 3.6 between what the itemized log says I used and what was debited against my plan.
Environment
| Client | OpenCode 1.18.21 |
| Plan | OpenCode Go |
| Models | gpt-5.6-luna, kimi-k2.7-code |
| Date | August 23, 2026, UTC-05 |
What happened
At 3:13 PM the client stopped with:
5 hour usage limit reached. It will reset in 2 hours 40 minutes.
To continue using this model now, enable usage from your available balance
The subscription page confirmed it:
- Continuous usage: 100% — resets in 2h 36m
- Weekly usage: 41%
- Monthly usage: 20%
Per the Go docs, the limits are $12 / 5h, $30 / week, $60 / month. So those bars translate to $12.00, $12.30 and $12.00 respectively. All three independently agree that ~$12 of usage was recorded.
What the usage log actually shows
The reset was scheduled for 5:49 PM, so the 5-hour window began at ~12:49 PM. I paged through the entire Usage History for that window and summed every row — 3 pages, 124 requests, 12:52 PM to 3:13 PM:
| Page | Time range | Requests | Cost |
|---|---|---|---|
| 3 (oldest) | 12:52 PM – 1:23 PM | 24 | $0.3806 |
| 2 | 1:24 PM – 1:44 PM | 50 | $0.8648 |
| 1 (newest) | 1:44 PM – 3:13 PM | 50 | $2.0612 |
| Total | 12:52 PM – 3:13 PM | 124 | $3.3066 |
Two points that rule out the obvious explanations:
- The oldest row in the log (12:52 PM) sits at the very start of the 5-hour window. This is not earlier activity falling outside the pages I reviewed.
- The weekly bar ($12.30) and monthly bar ($12.00) read essentially the same figure as the 5-hour bar. Virtually all of my usage this week and this month happened inside this one window. There is no activity elsewhere that could account for the missing ~$8.69.
Questions
- Why does the itemized usage log total $3.31 while every meter reports $12.00?
- Is usage debited against plan limits at the same dollar figure shown in the usage log, or at a different rate? The docs state limits are "defined in dollar value" but do not disclose that the log and the meter might use different figures.
- Does the Usage History page show every billed request, or is it filtered/truncated?
Related
This looks like the same class of problem as #11170 — overcharge relative to itemized usage, no published support channel, and a usage page that paginates at 50 rows with no export. That issue was labelled a bug and assigned, but I see no public resolution.
Requests
- A complete, exportable itemized record of requests billed against an account for a given day, including the amount debited against the plan limit for each.
- An explanation of the discrepancy between the log and the meters.
- If the log is accurate, restoration of the ~$8.69 of quota consumed without a corresponding record.
I have screenshots of the usage log, the limit dialog and the subscription page, and can share them. I have also emailed help@anoma.ly (the only contact I could find, and only by reading the Terms of Service — there is no support contact published anywhere on opencode.ai).
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.