Repository navigation
Bug: Console Go provider.only: tencent breaks routing for mimo-v2.5 #45996
Description
Description Console Go (opencode-go) is applying a provider.only: tencent preference that blocks access to mimo-v2.5. The model was working perfectly until ~30 minutes ago, then started consistently failing with a 404 error.
[404] No allowed providers are available for the selected model. Providers serving xiaomi/mimo-v2.5-20260422: gmicloud, deepinfra, xiaomi, parasail, streamlake, novita, but your request's provider.only preference permits only: tencent.
Expected behavior mimo-v2.5 should route to any of the available upstream providers (gmicloud, deepinfra, xiaomi, parasail, streamlake, novita) as it did before.
Actual behavior The backend forces provider.only: tencent, which does not serve mimo-v2.5, causing a 404.
Affected models
opencode-go/mimo-v2.5
opencode/mimo-v2.5-free (also affected)
Environment
OpenCode version: 1.18.25
Platform: Windows
Provider: Console Go (opencode-go)
Model: mimo-v2.5
Additional notes
This is a server-side bug in the /zen/go/v1 endpoint. The /zen/v1 (Zen) endpoint works fine.
Client-side config overrides (e.g. setting provider.only in opencode.jsonc) are ignored because the backend preference takes precedence.
The issue appeared suddenly after a backend change ~30 min ago; no client configuration was modified.
Request Please fix provider routing for mimo-v2.5 in Console Go. The provider.only: tencent preference should not be applied to models that Tencent does not serve.
Activity
github-actions commentedon Aug 28, 2026
This issue might be a duplicate of existing issues. Please check:
provider.only: tencentblocking mimo-v2.5 with a 404 on the Console Go endpoint, reported the same day with an identical error message and root cause description.If these describe the same underlying problem, consider consolidating into one issue so it's easier for maintainers to track.
J-eremy commentedon Aug 28, 2026
I manage multiple LiteLLM proxies for people, most of them are configured exactly the same. They are all different users and use their own account to connect. This bug is happening on some of them but not others trying to use the same model on each.
This might be a rollout thing? where no everyone is affected?
userhubgitia commentedon Aug 28, 2026
Same error reported using OpenCode Desktop (not Console Go):
Upstream request failed: [404] No allowed providers are available for the selected model. Providers serving xiaomi/mimo-v2.5-20260422: gmicloud, deepinfra, xiaomi, parasail, streamlake, novita, but your request's provider.only preference permits only: tencent.
Platform: Windows
Interface: OpenCode Desktop
Model: xiaomi/mimo-v2.5-20260422
Confirms that this bug affects both Console Go and Desktop — the issue is server-side on the /zen/go/v1 endpoint.
Dev8054445 commentedon Aug 28, 2026
I can confirm—there is indeed a problem; it started about an hour ago.
epulla commentedon Aug 28, 2026
confirmed as well. There's an issue with mimo v2.5 pro
golias17 commentedon Aug 28, 2026
Also having the same problem
golias17 commentedon Aug 28, 2026
Creating a new api key solved my issue.
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊