Repository navigation
[BUG] OpenCode Go deepseek-v4-flash returns HTTP 500 while mimo-v2.5 works #40480
Closed as not planned
Description
Description
Description
deepseek-v4-flash on OpenCode Go does not return a response in the
OpenCode client. A direct API request eventually returns HTTP 500.
The same API key, endpoint, machine, and network work correctly with
mimo-v2.5, which returns HTTP 200.
Steps to reproduce
curl -sS --max-time 90 \
-D - \
https://opencode.ai/zen/go/v1/chat/completions \
-H "Authorization: Bearer REDACTED" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-flash",
"messages": [
{
"role": "user",
"content": "Reply exactly with: OK"
}
],
"stream": false
}'Actual Result
HTTP/1.1 500 Internal Server Error
{"type":"error","error":{"type":"error","message":"Internal server error"}}
Control test
Changing only the model to mimo-v2.5 returns HTTP 200 and:
{"message":{"role":"assistant","content":"OK"}}
Request information
Model: deepseek-v4-flash
Endpoint: /zen/go/v1/chat/completions
Time: 2026-08-04 14:23:31 GMT
CF-RAY: a25e368a4a736814-SEA
Stream: false
Tools: none
OpenCode Go China-hosted model opt-in: enabled
Environment
OS: Debian Linux
Client: OpenCode Desktop
Network: Clash/Mihomo proxy
IPv4 connection and TLS handshake succeed
/zen/go/v1/models returns HTTP 200
mimo-v2.5 completion returns HTTP 200
Plugins
none
OpenCode version
1.18.13
Steps to reproduce
curl -sS --max-time 90 \
-D - \
https://opencode.ai/zen/go/v1/chat/completions \
-H "Authorization: Bearer REDACTED" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-flash",
"messages": [
{
"role": "user",
"content": "Reply exactly with: OK"
}
],
"stream": false
}'Screenshot and/or share link
No response
Operating System
Debian Linux 13.5
Terminal
QTerminal
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 4, 2026
This issue might be a duplicate of existing issues. Please check:
/zen/go/v1/chat/completions(same endpoint, same error)deepseek-v4-flashon opencode-go drops connection before response (same model, same endpoint)adminplocket commentedon Aug 4, 2026
I confirm the issue
ryanmargono commentedon Aug 4, 2026
seeign the same issue
GitHubrre commentedon Aug 4, 2026
Same issue deepseek fail to connect right now
tobioyelekan commentedon Aug 4, 2026
Experiencing same issue
leirbag4 commentedon Aug 4, 2026
confirmed issue
GitHubrre commentedon Aug 4, 2026
This is a server-side issue with the opencode provider, not a configuration problem on your end. The model is being correctly selected but the API calls are failing.
lordrebel commentedon Aug 4, 2026
Additional evidence from a user in UTC+8 (Beijing) — confirming this is a server-side routing issue, not client/config. Our instance hit the exact same failure window.
Timeline (Beijing time = UTC+8):
deepseek-v4-flashvia opencode-go consistently failingObserved error signature (from our gateway logs, all
provider=opencode-gomodel=deepseek-v4-flash):Request timed outEmptyStreamError— HTTP 200 SSE but 0 bytes, hung 200–330s then returned empty stream with no finish_reasonRemoteProtocolError, 2×APIConnectionErrorGET /zen/go/v1/modelsalso intermittently timed out during the window (while POST to other models worked)Key discriminator (matches #40465/#40485): same key, same endpoint, same machine —
deepseek-v4-flashfails whiledeepseek-v4-pro,mimo-v2.5,minimax-m3all return 200. Only the flash route is broken.Other notes for the post-mortem:
Config/test details: opencode-go subscription key,
POST https://opencode.ai/zen/go/v1/chat/completions. Happy to run more probes or paste sanitized logs if it helps the fix.Note: This comment was drafted with AI assistance and published with the user's authorization. (本评论由 AI 辅助撰写，经用户授权发布。)
Enough1122 commentedon Aug 8, 2026
Following up — same symptom as reported here (HTTP failure on
/zen/go/v1/chat/completionsfordeepseek-v4-flash, other models on the same key/endpoint still 200). Adding two new data points that I don't see in this thread yet:1. The 400 / 500 / "Model is unavailable" responses are transport-dependent (Anthropic vs OpenAI wire), not just server-side fluctuation.
I ran both endpoints against the same Go subscription key, same account, same machine, seconds apart:
POST https://opencode.ai/zen/go/v1/chat/completionsError from provider (Console Go): Upstream request failed: Model is unavailable.POST https://opencode.ai/zen/go/v1/messagesmodel: deepseek-v4-flash,stop_reason: max_tokensSo the
zen/gohost is currently serving deepseek-v4-flash on the Anthropic wire (/v1/messages) but rejecting the same request on the OpenAI-compatible wire (/v1/chat/completions). That's not a hang or rate-limit — it's a per-wire routing-level failure on the host that Anomaly routes Flash through.2. The official OpenCode CLI gets it right because it doesn't use Console Go for this model.
opencode.exe run -m opencode-go/deepseek-v4-flash "hi"returns a valid response immediately after the samechat_completionscall returns 400. Internal logger:So the CLI's opencode-go provider is reaching DeepSeek through a different upstream path than the
/zen/go/v1/chat/completionsendpoint. The CLI path is the one that's currently healthy; the public HTTPchat_completionsroute is the one that's broken.Implication for downstream clients
Third-party OpenAI-compatible callers (Hermes, custom scripts, CI bots, anything that hits the Go subscription via the documented
chat/completionsendpoint) are all blocked on the same wire, even though the model itself is up and the same account is happily serving via the CLI. Commenting here since this thread has the most concentrated community signal — same model, same endpoint, same failure window.Mirrors my earlier report at #41211 (opened Aug 8, now closing as duplicate of this thread). Happy to share sanitized curl/response diffs if useful.
github-actions commentedon Oct 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.