You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode Go quota dashboard cannot fetch real quota data #3844
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).
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. 🙏
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. 🙏
Activity
adivekar-utexas commentedon Jun 14, 2026
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).
diegosouzapw commentedon Jun 14, 2026
Hi @adivekar-utexas! Thanks for the precise diagnosis (and for PR #3838). 🙏 Confirmed on our side:
open-sse/services/usage.ts:1470,1538), but OpenCode doesn't expose a public quota/balance API yet (.../zen/go/v1/quota→ 404), so there's nothing real to fetch until upstream ships one (Feature Request: Add Zen balance API endpoint anomalyco/opencode#10448). The diagnostic latched-warning in PR fix(quota): surface OpenCode Go missing-quota-API as a latched warning #3838 is the right interim handling.usage_history) against a manualprovider_plansrequests/{hourly,weekly}dimension, and skip the connection once over its cutoff. That gives quota-aware routing for opencode-go (and every other fetcher-less provider) with zero upstream support.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. 🙏
diegosouzapw commentedon Jun 20, 2026
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:
.../zen/go/v1/quota→ 404, and theapi.z.aidefault rejects opencode-go keys with{"code":401}. There is nothing real to fetch until upstream ships an endpoint (tracked at Feature Request: Add Zen balance API endpoint anomalyco/opencode#10448 for Zen balance and [FEATURE]: Add Go plan usage/balance API endpoint (rolling/weekly/monthly windows) anomalyco/opencode#16017 for Go usage windows).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. 🙏