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
Some models like minimax don't have any variants specified by default, so ctrl+t does nothing.
The default opencode grok code fast 1 model does contain variants for different thinking levels that ctrl+t will cycle between, but will result in the error Bad Request: Model grok-code does not support parameter reasoningEffort.
These issues address the broader challenge of properly handling model variants and reasoning efforts across different contexts. Your specific case with grok-code and minimax models lacking variant support appears to be part of the larger model variant system being improved.
For keybind-related issues, please also check our pinned keybinds documentation: #4997
Feel free to ignore if none of these address your specific case.
The issue isn't that grok-code lacks variant support. The issue is the default model configuration for grok-code contains variants that aren't actually supported and give errors if you select them.
chindris-mihai-alexandru commented on Jan 18, 2026
This also occurs on the first message (not just after the Ctrl+T variant cycles) on v1.1.25:
the Grok API returns {"code":"Client specified an invalid argument","error":"Invalid arguments passed to the model."} which then causes a secondary AI_TypeValidationError because the error format is a string instead of the expected object schema.
Activity
github-actions commentedon Jan 11, 2026
This issue might be a duplicate of existing issues. Please check:
--variantflag to rootopencodecommand #7354: Add--variantflag to rootopencodecommandThese issues address the broader challenge of properly handling model variants and reasoning efforts across different contexts. Your specific case with grok-code and minimax models lacking variant support appears to be part of the larger model variant system being improved.
For keybind-related issues, please also check our pinned keybinds documentation: #4997
Feel free to ignore if none of these address your specific case.
bo-tato commentedon Jan 11, 2026
The issue isn't that grok-code lacks variant support. The issue is the default model configuration for grok-code contains variants that aren't actually supported and give errors if you select them.
chindris-mihai-alexandru commentedon Jan 18, 2026
This also occurs on the first message (not just after the Ctrl+T variant cycles) on v1.1.25:
the Grok API returns {"code":"Client specified an invalid argument","error":"Invalid arguments passed to the model."} which then causes a secondary AI_TypeValidationError because the error format is a string instead of the expected object schema.
rekram1-node commentedon Jan 18, 2026
fixed:
d841e70