anomalyco / anomalyco/opencode
OpenCode Go quota usage appears ~4x higher than displayed DeepSeek V4 Flash cost
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Possible OpenCode Go usage metering discrepancy with DeepSeek V4 Flash
I’m seeing a discrepancy between the cost shown in the usage graph and the Go quota consumption for deepseek-v4-flash.
On Aug 17, the usage graph shows:
deepseek-v4-flash (go): $3.31
At approximately the same time, my Go limits showed:
5-hour usage: 100%
Weekly usage: 44%
Monthly usage: 22%
According to the Go documentation, these limits correspond to $12 / $30 / $60 of usage respectively.
Therefore:
44% of $30 ≈ $13.20
22% of $60 ≈ $13.20
This is almost exactly 4x the $3.31 shown in the cost graph.
I was only using opencode-go/deepseek-v4-flash for this workload.
Could you confirm whether the Go quota meter uses a different internal cost multiplier than the cost shown in the usage graph for DeepSeek V4 Flash?
If not, there may be a roughly 4x discrepancy in quota accounting.
I can provide screenshots and detailed session/token usage logs if useful.
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.
Research direction
Start by tracing the usage graph and Go quota accounting for deepseek-v4-flash, using the reported $3.31 cost, 44% weekly usage, and 22% monthly usage as comparison points. Confirm whether both meters use the same internal cost basis; done means documenting the multiplier or reproducing and correcting the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100