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
[Bug] OpenCode Go: some models return 403 Forbidden: {"model":"<model>"} while others work (subscription active, limits not reached) #40343
Using the OpenCode Go provider (opencode-go) with an active subscription and API key, certain models fail with AI_APICallError: Forbidden. The error body echoes the requested model id:
Forbidden: {"model":"mimo-v2.5"}
The subscription is active and usage limits are not exhausted. Other Go models work fine with the same key.
Environment
opencode version: 1.18.11
OS: Windows
Provider: opencode-go (OpenCode Go subscription)
Key type: sk-... API key from the Zen console
Models affected
With the same API key, direct requests to https://opencode.ai/zen/go/v1/chat/completions:
Model
Status
mimo-v2.5
403{"model":"mimo-v2.5"}
mimo-v2.5-pro
403{"model":"mimo-v2.5-pro"}
hy3
403{"model":"hy3"}
gpt-5.6-luna (via /responses)
403
deepseek-v4-flash
200 OK
deepseek-v4-pro
200 OK
glm-5.2
200 OK
glm-5.1
200 OK
kimi-k3
200 OK
kimi-k2.7-code
200 OK
qwen3.8-max
200 OK
grok-4.5
500 (separate server error)
The affected models are listed in the gateway's catalog (GET https://opencode.ai/zen/go/v1/models includes mimo-v2.5, mimo-v2.5-pro, hy3, gpt-5.6-luna), so this is an authorization/entitlement decision, not "unknown model".
Not user-agent dependent (tested opencode, opencode/1.18.11, Mozilla/5.0 ..., curl/8.0, Python-urllib/3.11 — all return the same 403 body for the affected models; only Python-urllib triggers the separate Cloudflare 1010 block).
Expected behavior
All models advertised for the Go subscription (including mimo-v2.5) should be usable while the subscription is active and limits are not reached.
Activity
huashuhuashu720 commentedon Aug 4, 2026
+1
denis-protivensky commentedon Aug 11, 2026
I have the same issue:
Works (HTTP 200): deepseek-v4-flash, deepseek-v4-pro, minimax-m3, minimax-m2.7, qwen3.5-plus.
Fails (HTTP 403): mimo-v2.5, mimo-v2.5-pro, mimo-v2-pro, mimo-v2-omni, hy3, minimax-m2.5.
Repro:
'{"model":"mimo-v2.5","messages":[{"role":"user","content":"hi"}],"max_tokens":8}' → 403.
Belf1995 commentedon Sep 7, 2026
Has the solution to the problem still not been found?
fix: recognise real OpenCode Go keys, and correct the Go catalog
fix: revert the key-shape change; Go keys are oc_sk_, not sk-
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
fix: recognise real OpenCode Go keys, and correct the Go catalog
fix: revert the key-shape change; Go keys are oc_sk_, not sk-
fix: recognise real OpenCode Go keys, and correct the Go catalog
fix: revert the key-shape change; Go keys are oc_sk_, not sk-
fix: recognise real OpenCode Go keys, and correct the Go catalog
fix: revert the key-shape change; Go keys are oc_sk_, not sk-
fix: recognise real OpenCode Go keys, and correct the Go catalog
fix: revert the key-shape change; Go keys are oc_sk_, not sk-