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.
True, I can get fired from my job, because of Grok My teammates are pointing out at the stupid errors and I have to explain it now how could this happened.
Please, I understand that now Elon is the boss, but forcing Grok to be enabled and getting bad code experience (even if Grok is getting better on the data training) is a frustration thing and the product is getting worse.
If somebody wants to use it - let’s allow them, but not me.
I even started to consider Junie from IntelliJ, where is Windsurf btw?
If you wont’ stop we have to switch. It was a good product, but with this forcing - it feels not like that anymore now.
This is actually insanity, i am on a unlimited auto (until renewal in September and only use specific models for specific use. With this switch you basically drained all my credits without my approval. So are you going to refund me for this change?)
Was considering renewal on at larger subscription when this one is finished, but i can’t really use Cursor in the current state.
Thanks for flagging this. The behavior where Grok 4.5 was getting force‑enabled and set as your default regardless of your selection has been addressed in the latest stable - update to the newest version (Cursor → Check for Updates) and your model choice should stick. If you still see a model being enabled or selected that you didn’t pick after updating, reply here with your version and a screenshot and I’ll dig in. (For anything billing‑related, drop us a note at [email protected] and we’ll take a look.)
Tnis is an utter crock. Nobody wants to use Grok and I don’t believe this was an unintentional “bug.” Forcing people onto your own model against their will is just hostile.
My teammates are pointing out at the stupid errors and I have to explain it now how could this happened.