Skip to content

[Subscriber Alert] OpenCode Go billing failure: Kimi disabled due to "insufficient balance" on proxy account #24470

Closed as not planned
Closed as not planned
[Subscriber Alert] OpenCode Go billing failure: Kimi disabled due to "insufficient balance" on proxy account#24470
Assignees
jlongster

Description

@capem
capem
opened on Apr 26, 2026

Description

As a paying OpenCode Go subscriber, I am currently unable to use the Kimi models. The session is stuck in a permanent loop: Provider returned error [retrying in 5s attempt #3].

My debug logs reveal a critical backend failure. The OpenCode Go proxy is hitting a billing suspension on the upstream Moonshot AI account. The raw error log explicitly states:
"Your account org-446a70bb... is suspended due to insufficient balance, please recharge your account".

Furthermore, the CLI (v1.14.25) is mishandling this 429 error by treating it as a retryable rate limit instead of a fatal billing error, leading to the infinite UI hang.

Plugins

None

OpenCode version

1.14.25

Steps to reproduce

  1. Use OpenCode Go subscription.
  2. Attempt to run a prompt using Kimi K2.6/2.5.
  3. Observe the red error box and the persistent "retrying in 5s" loop.
  4. Check debug logs to confirm the exceeded_current_quota_error from the Moonshot org account.

Screenshot and/or share link

No response

Operating System

CachyOs

Terminal

konsole 26.04.0

Activity

  1. capem
    added
    bugSomething isn't working
    on Apr 26, 2026
  2. github-actions
    assigned
    rekram1-node
    on Apr 26, 2026
  3. github-actions
    added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 26, 2026

  4. github-actions commented on Apr 26, 2026

    @github-actions
    github-actionsBot
    on Apr 26, 2026 – with GitHub Actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your issue is the same, please consider adding a comment there instead of opening a new one. If it's distinct, please clarify what differentiates it from those reports.

  5. thdxr
    removed
    bugSomething isn't working
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  6. thdxr
    assigned
    jlongster
    and unassigned
    rekram1-node
    on May 3, 2026

  7. github-actions commented on Jul 4, 2026

    @github-actions
    github-actionsBot
    on Jul 4, 2026 – with 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.

  8. github-actions
    closed this as not plannedon Jul 4, 2026
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