Skip to content

Usage percentage appears to be significantly higher than actual model cost #43609

Closed as duplicate

Description

@BaiShou

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

Activity

  1. github-actions commented on Aug 20, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of several existing issues reporting the same discrepancy between visible model costs and the OpenCode Go usage percentage. Please check:

    If your issue is the same, please consider adding a reaction or comment to one of the existing reports instead of opening a new one.

  2. neriousy commented on Oct 20, 2026

    @neriousy
    Member

    We're tracking this in #42985, so I'm closing this as a duplicate. Please follow that issue for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions