anomalyco / anomalyco/opencode

Usage percentage appears to be significantly higher than actual model cost

Open
#43,609 1 comment 1 reaction 1 assignee View on GitHub

@fwang is already working on this.

Since Aug 20, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

Usage percentage appears to be significantly higher than actual model cost

Description

I noticed a significant discrepancy between the actual model cost shown in my usage details and the monthly Usage percentage shown in OpenCode Go.

Over the past few days, my usage was approximately:

DeepSeek V4 Flash

  • $0.63
  • $0.97
  • $0.13
  • $2.45
  • $3.77
  • $1.77

Total: $9.72

Luna

  • $2.68
  • $1.29

Total: $3.97

Therefore, my total visible model cost is:

$9.72 + $3.97 = $13.69

However, my OpenCode Go monthly Usage is already showing 49%.

If the monthly Usage limit is $60, then 49% corresponds to approximately:

$60 × 49% = $29.40

This means the dashboard appears to be counting approximately $29.40 of Usage while the visible model costs add up to only $13.69, or about 2.15× the visible cost.

Questions

Could you clarify how OpenCode Go calculates Usage percentage?

Specifically:

  1. Is the $60 monthly limit based on actual model API cost, or is there an internal Usage conversion/rate?
  2. Does DeepSeek V4 Flash have a different Usage multiplier?
  3. Does Luna have a different Usage multiplier?
  4. Why does approximately $13.69 of visible model cost result in approximately 49% of the $60 monthly Usage quota?
  5. Is the Usage percentage shown in the dashboard expected to behave this way?

I'm mainly trying to understand whether 49% usage is correct, or whether there may be an issue with the Usage calculation/display.

Thanks!

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.