Where does the bug appear (feature/product)? Cursor IDE Describe the Bug 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. Operating System Windows 10/11 Version Information Version: 3.12.30 (user setup) VS Code Extension API: 1.128.0 Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480 Date: 2026-07-21T22:50:03.568Z Layout: IDE Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Windows_NT x64 10.0.26200 For AI issues: which model did you use? GPT 5.6 Terra High Additional Information Marking as un-usable because with the model getting force set to Grok and Grok not being approved at my Org, cursor is essentially un-usable. Does this stop you from using Cursor Yes - Cursor is unusable

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.

Still getting autoswapped to Grok after following the above. RequestId: e9f86db5-492f-4548-ac71-a1750fa75ff8 [image] 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.

How can we permanently block grok? It sucks for coding.

Updated cursor to latest and restarted multiple times and this is still happening. Every new chat and subagent defaults to Grok, even if disabled. [image]

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.

Same issue for me Version: 3.12.30 VS Code Extension API: 1.128.0 Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480 Date: 2026-07-21T22:50:03.568Z Layout: IDE Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Linux x64 7.0.0-28-generic As a note: I’ve downgraded my plan until this is fixed and am testing alternatives in the meantime. My entire workspace including technical and non technical projects runs out of cursor, I use it as a giant cowork, and I love the composer model. Once the space-x deal was announced I started planning an exit route in case things exactly like this became the norm. It might be an honest bug but the optics are terrible and this situation reads like an Onion article.

I have two Cursor subscriptions (individual and teams), and I’m considering migrating to Kimi if Cursor team forces us to use Grok more and more. I hope we get a Composer 3 in the future or get Grok improved in a near future (fixing issues like Grok 4.5 cannot use AskQuestion tool; falls back to inline questions (Composer 2.5 works) - #32 by ctewalt.aiworldwide)

True, I can get fired from my job, because of Grok :grinning_face_with_smiling_eyes: 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. Thanks!

have same problem very annoying

Cursor IDE force enabling Grok 4.5 and setting as default model, regardless of my initial selection

Support Bug Reports

kvothe (Kvothe) July 22, 2026, 7:45pm 9

Topic		Replies	Views
Model selection switching to grok 4.5 Bug Reports grok	6	544	September 17, 2026
Grok re-enables itself after being disabled in Settings Bug Reports chat , grok	29	1486	October 6, 2026
Grok set as default every time Bug Reports auto-mode , grok	12	771	September 29, 2026
Please keep Grok's fingers off my model settings Feedback grok	3	182	August 28, 2026
Stop defaulting to Grok 4.6 High PLEASE! Feedback installation , grok	2	300	September 2, 2026

Cursor IDE force enabling Grok 4.5 and setting as default model, regardless of my initial selection

Related topics