Repository navigation
Console Go (zen/go/v1): mimo-v2-pro and mimo-v2-omni always fail with 'Upstream request failed' #39873
Closed as not planned
Description
Summary
mimo-v2-pro and mimo-v2-omni are listed in GET /zen/go/v1/models but every completion request fails with invalid_request_error: Upstream request failed. Persistent across repeated attempts and timeouts (30s/60s).
Repro
curl -s https://opencode.ai/zen/go/v1/chat/completions \
-H "Authorization: Bearer <key>" -H "Content-Type: application/json" \
-d '{"model":"mimo-v2-pro","messages":[{"role":"user","content":"hi"}],"max_tokens":10}'Response (6/6 attempts failed, 2026-07-31)
{"error":{"message":"Error from provider (Console Go): Upstream request failed","type":"invalid_request_error","param":null,"code":"invalid_request_error"}}Impact
- Both models listed as available but are unusable → agent auto-fallback wastes turns retrying
- Sibling models
mimo-v2.5-pro/mimo-v2.5work fine on the same key
Expected
- Either fix upstream routing, or remove/replace these models in
/modelsuntil healthy
Environment
- Endpoint: https://opencode.ai/zen/go/v1 (Console Go)
- Same key successfully used for 20+ other models on the same endpoint
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jul 31, 2026
This issue might be a duplicate of existing issues. Please check:
huangcihang1-hub commentedon Aug 1, 2026
May I ask if your issue has been resolved? I am also experiencing the same problem, and I have even used multiple accounts — all of them have encountered this issue.
github-actions commentedon Oct 1, 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.