anomalyco / anomalyco/opencode
OpenCode Go quota usage inconsistency: Monthly usage percentage exceeds Weekly usage percentage with mismatched cost statistics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Possible OpenCode Go quota metering logic bug and cost accounting mismatch when using deepseek-v4-flash (go)
I observe abnormal inconsistent quota percentages on my OpenCode Go subscription dashboard, alongside mismatches between the billed cost chart and quota consumption:
Current dashboard metrics:
- Rolling Usage: 15%
- Weekly Usage: 65%
- Monthly Usage: 58%
According to the OpenCode Go quota rules, the monthly usage percentage should never be lower than weekly usage percentage at any point in the billing cycle. Right now my Monthly Usage (58%) < Weekly Usage (65%), which is logically impossible and indicates broken quota calculation logic.
Meanwhile, I can see the cost trend on my usage chart:
- Aug 16: deepseek-v4-flash (go): $1.87
- Aug 17: deepseek-v4-flash (go): $8.42
My workload only routed traffic through opencode-go/deepseek-v4-flash during this period. The consumed quota percentage does not align with the dollar amount shown in the cost breakdown chart.
Could you investigate two issues:
- Why Monthly Usage percentage is lower than Weekly Usage percentage; this breaks the expected rolling/period quota logic.
- Verify whether the quota consumption meter uses identical pricing data as the daily cost graph for deepseek-v4-flash. There appears to be a mismatch between the dollar value displayed in the cost chart and the quota percentage consumed.
I can supply all attached screenshots, raw timestamps and token usage logs for further debugging if required.
Plugins
No plugins were used
OpenCode version
1.18.18.0
Steps to reproduce
- Subscribe to OpenCode Go
- Send continuous requests to
opencode-go/deepseek-v4-flash - Observe the quota percentage panel and daily cost chart
Screenshot and/or share link
Operating System
Windows 11
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.
Research direction
No source files or tests are named; start by reproducing the dashboard and cost-chart behavior in OpenCode 1.18.18.0 with opencode-go/deepseek-v4-flash. Compare weekly and monthly quota percentages with the daily cost values and supplied usage logs. Done means the quota ordering and cost accounting are consistent, or the remaining discrepancy is documented with reproducible evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100