You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After upgrading from 1.19 to 2.0, attempting to switch Mimo reasoning replies "does not support any variants" #58897
I followed directions to 'upgrade' 1.19 to 2.0, but model reasoning appears to have been downgraded. Current reasoning effort is no longer shown on model selection line. Attempts to use /variant or /effort or /thinking command displays a "does not support any variants" message. However, according to xiaomi docs, the MiMo-V2.6-Flash model should accept 'none', 'low' and 'high' reasoning efforts (amonst other aliases).
Thanks for the report! I think this is a duplicate of #51541.
In OpenCode 2.x, MiMo models come from the provider catalog with only an on/off thinking toggle (no effort levels), and they use the generic OpenAI-compatible provider package. OpenCode doesn't currently build any variants for a toggle on that package, so /variant reports that the model doesn't support any. #51541 describes exactly this, using the Xiaomi token-plan MiMo v2.6 models as its example.
Possible duplicates and related issues, ordered by likelihood:
It's currently not allowing one to 'toggle' the reasoning on or off either; their own web page indicates they support a number of values "... When set to none, reasoning is disabled; all other valid values map to enabled reasoning. The value minimal is mapped to low. Values xhigh, max and ultra are mapped to high". That other bug was opened a month ago.
Closing this as a duplicate of #51541, since we haven't heard back. That issue tracks the same problem: Xiaomi MiMo token-plan models (including MiMo-V2.6) only have an on/off thinking toggle on the OpenAI-compatible provider package, OpenCode builds no reasoning variants for that, and so /variant says the model doesn't support any. Please follow #51541 for updates. If your problem turns out to be different, reply here and we can reopen.
What do you mean by "haven't heard back"? i responded, and instead of explaining why you can't either simply map to the values that they support, or revert the code to known working good state within a month, you want me to duplicate my efforts in a bug report whose 'toggle' premise isn't entirely supported by the provided mimo documentation?
Activity
opencode-agent commentedon Oct 25, 2026
Thanks for the report! I think this is a duplicate of #51541.
In OpenCode 2.x, MiMo models come from the provider catalog with only an on/off thinking toggle (no effort levels), and they use the generic OpenAI-compatible provider package. OpenCode doesn't currently build any variants for a toggle on that package, so
/variantreports that the model doesn't support any. #51541 describes exactly this, using the Xiaomi token-plan MiMo v2.6 models as its example.Possible duplicates and related issues, ordered by likelihood:
@ai-sdk/openai-compatible(including all Xiaomi MiMo token-plan models) get zero variants. Same problem.reasoning_effortvalues for mimo-v2.6-flash.The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. You can follow #51541 for updates.
DXXS commentedon Oct 25, 2026
It's currently not allowing one to 'toggle' the reasoning on or off either; their own web page indicates they support a number of values "... When set to none, reasoning is disabled; all other valid values map to enabled reasoning. The value minimal is mapped to low. Values xhigh, max and ultra are mapped to high". That other bug was opened a month ago.
Why don't you just revert the code to 1.19?
opencode-agent commentedon Oct 26, 2026
Closing this as a duplicate of #51541, since we haven't heard back. That issue tracks the same problem: Xiaomi MiMo token-plan models (including MiMo-V2.6) only have an on/off thinking toggle on the OpenAI-compatible provider package, OpenCode builds no reasoning variants for that, and so
/variantsays the model doesn't support any. Please follow #51541 for updates. If your problem turns out to be different, reply here and we can reopen.DXXS commentedon Oct 26, 2026
What do you mean by "haven't heard back"? i responded, and instead of explaining why you can't either simply map to the values that they support, or revert the code to known working good state within a month, you want me to duplicate my efforts in a bug report whose 'toggle' premise isn't entirely supported by the provided mimo documentation?