I recently installed the latest Cursor update today and it seems to have broken all model selection settings. I am being forced to use Grok 4.5 High Fast regardless of what model I initialize. Even if I disable Grok 4.5 in the model provider lists, if I start a thread with another model (such as GPT 5.6), Grok 4.5 High Fast is re-enabled and overwrites my selected model. This is an extreme breach of trust/security that the IDE can overwrite and ignore my model provider settings, as Grok is not an approved model for my organization. So I will be unable to continue using cursor until this is resolved.
Steps to Reproduce
Open cursor on the affected version.
Disable Grok 4.5 in the model list
Start a thread with another model provider, such as GPT 5.6 Terra High.
Expected Behavior
Expected behavior: Grok 4.5 stays disabled and the agent runs using GPT 5.6 Terra.
Actual behavior: Grok 4.5 is force re-enabled and set to high fast.
Hi @ZakThompsonEchelon Thanks for the detailed report, and I understand the concern. A model you disabled getting switched on and used, especially one that isn’t approved for your org, shouldn’t happen.
This is a bug on our side, not your settings. We were running a promotion suggesting Grok 4.5 for new chats, and a bug meant it could override your selected model and re-enable Grok even after you turned it off. That promotion has now been rolled back, so new chats should no longer be pushed to Grok.
Because an earlier switch can stick locally, please do this once: update and restart Cursor, re-select GPT 5.6 Terra High, and turn Grok off again in Settings > Models. Your choice should then hold. We’re also tracking a fix so a disabled model can’t be re-enabled this way at all.
Lmk if you’re still seeing this issue after taking these steps and I can suggest next steps.
EDIT: It seems that I’m able to at least use composer 2.5 now without it being forced to Grok, it seems like just third party models are the one’s being switched for me now. Unsure if that indicates a different potential issue.
Unfortunately, we’re experiencing the same issue on our end. We’ve tried multiple Cursor versions, and both the route model and the models themselves are disabled. It’s getting quite frustrating.
