Repository navigation
OpenCode Go: "Upstream request failed: Endpoint is unavailable" for qwen/grok models (server-side, not client network) #43163
Description
Description
Summary
OpenCode Go (Zen gateway) returns server_error: Error from provider (Console Go): Upstream request failed: Endpoint is unavailable. for qwen3.7-plus / qwen3.7-max / grok-4.5, while other Go models (kimi-k3, glm-5.2, minimax-m3, gpt-5.6-luna) work fine with the same API key. This is reproducible via direct curl calls to the gateway — not a client-side network/proxy issue.
Environment
- opencode CLI version: 1.18.11 (Windows 10, win32-x64)
- Auth: opencode-go provider, type "api" (Go subscription, bound via /connect)
- Default model: qwen3.7-plus
Reproduction (curl, no SDK involved)
POST https://opencode.ai/zen/go/v1/chat/completions
Authorization: Bearer
Content-Type: application/json
{"model":"qwen3.7-plus","messages":[{"role":"user","content":"hi"}],"stream":false,"max_tokens":16}
Actual response
{"error":{"type":"server_error","message":"Error from provider (Console Go): Upstream request failed: Endpoint is unavailable."}}
Observations
- Same error with and without HTTP proxy; gateway is reachable from here (HTTP 200 on /zen/go/v1/models).
- Model matrix with the same key:
- WORKS: kimi-k3, glm-5.2, minimax-m3, gpt-5.6-luna
- FAILS: qwen3.7-plus, qwen3.7-max, grok-4.5 -> "Upstream request failed: Endpoint is unavailable."
- The error string is NOT present in the opencode client binary, so it originates from the gateway's upstream provider ("Console Go").
- opencode log (opencode.log) shows:
AI_APICallError: Upstream request failed: Endpoint is unavailable.with providerID=opencode-go modelID=qwen3.7-plus, every request, 100% failure rate.
Expected
Chat completions succeed for all models listed in the Go model catalog.
Severity
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Activity
github-actions commentedon Aug 18, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct (e.g. a consistent 100% failure rate rather than intermittent, or a different root cause), please add a note clarifying how it differs from the above.
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊