anomalyco / anomalyco/opencode
Console Go (zen/go/v1): mimo-v2-pro and mimo-v2-omni always fail with 'Upstream request failed'
Open
@MrMushrooooom is already working on this.
Since Jul 31, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- Avg merge
- 7h 2m
- Merged PRs (30d)
- 384
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.