Skip to content

why tokens run so quickly? #37748

Closed as not planned
Closed as not planned

Description

@1273693845

Description

The label “Kimi K3 (2x usage)” is naturally understood as offering twice the usage allowance, especially because the Go promotional page states that Kimi K3 gets “2x usage limits.” However, my dashboard suggests the opposite: $5.85 of displayed K3 cost appears to count as approximately $11.70 against the five-hour quota. Together with $0.38 from other models, this exhausted the $12 limit.

The cost chart shows only approximately $6.23, while the quota meter shows 100% of a $12 limit, without displaying any weighted usage calculation. This is materially misleading. In addition, the K3 agent stopped during a file-write step and repeatedly returned “Upstream request failed,” without completing the task. Please clarify the multiplier, provide request-level records, and restore the quota consumed by abnormal retries.

Image Image

Plugins

none

OpenCode version

the latest

Steps to reproduce

recover my usage--- i dont want totally clear to 0, but please let it goes to normal usage just 6$
what i know is that i will more carefully use k3 or other expensive LLM from now on
stop using "2x usage" just say "spend double tokens" please

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. fadaishaitaiyang commented on Jul 24, 2026

    @fadaishaitaiyang

    same problem

  2. herimanantsoa51 commented on Jul 24, 2026

    @herimanantsoa51

    I have the exact same issue with my OpenCode Go subscription ($60/month plan).

    My situation:

    • 5-hour limit consumed way too fast despite very low actual spend
    • Monthly usage already at 37% in just 2 days
    • Total spent: less than $5

    The same discrepancy — usage meter claims far more consumption than the actual dollar amount shown.

    This is clearly a bug in limit calculation, not real usage. I filed a similar report here: #38570

    Please fix this — it's affecting many paying subscribers.

    P.S.: I have screenshots showing the same issue but am unable to attach them here via API. Check #38570 for full screenshots.

  3. kai-kleinbard-tyto commented on Jul 30, 2026

    @kai-kleinbard-tyto

    Closing — insufficient information to investigate (no template, no version, no repro steps, or support question). Please reopen with the Bug Report template.

  4. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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