Skip to content

OpenCode Go quota dashboard cannot fetch real quota data #3844

Closed

Description

@adivekar-utexas

OmniRoute currently exposes OpenCode Go quota UI/preflight hooks, but real OpenCode Go API keys do not return quota data from the configured endpoints. Verified with a valid key: chat completions work at https://opencode.ai/zen/go/v1/chat/completions, but https://opencode.ai/zen/go/v1/quota returns HTTP 404 and the dashboard default https://api.z.ai/api/monitor/usage/quota/limit returns JSON code 401 (token expired or incorrect). This means dashboard/quota shows No quota data for OpenCode Go accounts and quota-aware routing cannot make real decisions. PR #3838 is only a diagnostic mitigation: it makes this failure explicit and caches the 404; it does not implement real quota retrieval. Upstream OpenCode issue for the missing public API: anomalyco/opencode#10448 . Related OpenCode Go usage request: anomalyco/opencode#16017 .

Activity

  1. adivekar-utexas commented on Jun 14, 2026

    @adivekar-utexas
    ContributorAuthor

    Cross-linking related work: PR #3838 is a diagnostic mitigation for this issue. It does not implement quota retrieval because OpenCode does not currently expose a public quota API for Zen balance / Go usage. Upstream requests: anomalyco/opencode#10448 (Zen balance API) and anomalyco/opencode#16017 (Go usage windows).

  2. diegosouzapw commented on Jun 14, 2026

    @diegosouzapw
    Collaborator

    Hi @adivekar-utexas! Thanks for the precise diagnosis (and for PR #3838). 🙏 Confirmed on our side:

    We've folded opencode-go into #3709 as a second motivating provider (alongside ollama-cloud). Keeping this open while PR #3838 lands the diagnostic and #3709 tracks the real fix — we'll tag you on both. 🙏

  3. diegosouzapw commented on Jun 20, 2026

    @diegosouzapw
    Collaborator

    Closing this as upstream-blocked, with the realistic mitigation already shipped — and thank you again for the precise diagnosis and for PR #3838.

    Summary of where this lands:

    So there's no further OmniRoute-side work that would produce real quota data here. I'm closing this rather than leaving it open indefinitely against an upstream gap — but it's a "blocked on upstream", not a "won't do": the moment OpenCode publishes a usage/balance API, wiring a real probe for opencode-go is straightforward, and a comment here (or a fresh issue linking the upstream endpoint) will get it picked up immediately. Please do reopen if upstream ships it. 🙏

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

Metadata

Metadata

Assignees

No one assigned

    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