I switched off Grok in Settings → Models and I started new chat with another model (for example Fable 5). When I run command in chat it automatically changes to Grok
Steps to Reproduce
open Cursor
go to Settings → Model
switch off Grok
start new chat with Fable model (or other except for Grok)
run command in chat
Grok enables inself in settings and is used automatically in chat
Hey, thanks for the detailed report with steps and the screen recording. It really helps.
I looked into it and this is a bug on our side. In new chats, Cursor sometimes nudges you toward the recommended model right now that’s Grok 4.5, and it also re-enables it in Settings, ignoring that you explicitly turned it off and selected Fable 5. That shouldn’t happen. I reported it to the team.
There’s no separate option to disable this nudge yet, so there isn’t a clean workaround either. For now, you’ll need to re-select Fable 5 and optionally disable Grok again in each new chat. If you don’t want to end up on the more expensive Fast option, make sure Fast isn’t enabled in the picker.
I can’t share an ETA for a fix yet. Once I have an update, I’ll reply in this thread.
This exact same thing is happening to us right now except it’s changing from Auto to Composer 2.5. Composer isn’t disabled in settings, but it’s changing the model selection from Auto to Composer 2.5 after I send the message.
@jsmith what you’re describing sounds like a different case than this thread. This thread is about a disabled model that turns itself back on. In your case, Auto switches to Composer 2.5 after you send a message, nothing is disabled, and Router is off. We should track that separately so it doesn’t get mixed up with the current bug.
Please start a new thread for your case and include:
your Cursor version Settings > About and your OS
the Request ID from the message where Auto switched to Composer 2.5 top right chat menu > Copy Request ID
whether you’re hitting a usage or rate limit at that moment
if possible, a short screen recording
With those details, we can reproduce it properly and figure it out. Drop the link to the new thread here and we’ll take it.
I’m also noticing a lot of Fast (Composer and Grok) after being disabled them (except for the ones I can’t), but my main work was being done in Not-Fast and now seems a bit random. (at least haven’t found why or how to solve it).
Experiencing this as well. I’m guessing this is working as intended from the PM’s perspective, but some of us refuse to use software developed by that company. Strongly considering moving to another coding platform if this is not resolved soon, for what it’s worth.
The issue from the first post, where a model disabled in Settings > Models like Grok would turn itself back on and get auto selected in chat, was fixed in a recent update stable version 3.14.7. Please update to the latest version and this should go away. Disabled models now stay off, and auto switching will no longer pick them. Thanks to @Charles_Wood for confirming in #24.
Separately, about Fast turning itself back on with Grok 4.5 or Composer 2.5 @Ceneka, @jkpe, @Pol_Cors, this is a different issue and it is not covered by this fix. We are tracking it, but I can’t share an ETA yet. I’ll post here when I have an update.
If after updating to 3.14.7 you still see a disabled model being used, please reply with your version and the Request ID and we will take a look.
Disabled models now stay off, and auto switching will no longer pick them
That doesn’t seem to be the case. I’m running 3.14.7, and while disabled models do seem to stay off for now, from the usage tab at https://cursor.com/dashboard/usage, I gather that any time I pick “auto” Grok is used even though it’s disabled both as “Model” and as “Subagent model”.
At first I figured this happened because an existing chat in an existing project might continue to use the model it had been using before. But it also happens for new chats in projects created after upgrading to 3.14.7
Here’s the request ID of a request with the issue: 8f1b687f-e5c0-4e30-b337-01c095480ded
Quick update on this thread. The behavior it started with, where a model that’s disabled in Settings turns itself back on and replaces the model you picked in a new chat, was investigated, and recent updates include improvements for this.
If you’re still seeing it, please update to the latest Stable build, then check if it still happens. Cursor Settings > About will show your version. Some of the reports above are from older versions 3.11.x and 3.13.x.
If the issue still happens on the latest version, please share:
Your Cursor version and OS Cursor Settings > About
The Request ID from the message where the model switched by itself right top chat menu > Copy Request ID
Also, about a couple things from recent messages. Fast turning on by itself on Grok 4.5, and Plan sub-tasks going to Grok Fast, are most likely separate issues, not the same as the original report. If they still happen after updating, please start a separate thread for each one you can link back here so it’s easier to track and avoid mixing cases.