Cursor Ignores Disabled Models When Creating New Agents

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I disabled Grok in my Models list because I don’t want to use it.

However, whenever I create a new Agent chat, Cursor still automatically selects Grok as the default model (both Fast and High variants), even though I’ve explicitly disabled it.

This completely defeats the purpose of having a model management page.

If a model is disabled by the user, it should be treated as unavailable everywhere, including:

  • Default model selection
  • Automatic fallback
  • New Agent chats
  • Any automatic routing

Otherwise, the “Disable” option is misleading. Users expect disabled models to never be selected automatically.

Model preferences should always respect explicit user choices, not silently override them.

Please make disabled models truly disabled.

Steps to Reproduce

Steps to Reproduce

  1. Open Settings → Models.
  2. Disable Grok (Fast and High).
  3. Confirm that Grok no longer appears in the available model list.
  4. Create a new Agent chat.
  5. Observe the default model selected for the new Agent.

Expected Behavior

The new Agent should use one of the enabled models as the default. Disabled models should never be selected automatically.

Actual Behavior

The new Agent is still initialized with Grok (Fast/High) as the default model, even though it has been explicitly disabled in the Models settings.

Operating System

MacOS

Version Information

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: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report and steps. This is a bug on our side. In new chats, Cursor sometimes switches to the recommended model right now that’s Grok 4.5 and it also re-enables it in Settings, even if you explicitly turned it off. That shouldn’t happen. We already discussed this in another thread, and I’ve reported it internally.

There’s no separate option to disable this nudge yet, so there isn’t a clean workaround either. For now, you’ll need to reselect your preferred model and disable Grok again if you want in each new chat. To avoid the more expensive Fast option, make sure Fast is turned off in the model picker.

I can’t share an ETA for the fix yet. I’ll post an update in the thread as soon as I have one.

8

Hey @CrazyWeeds, quick update on this thread.

The issue where new Agent chats would auto-select Grok and re-enable it in Settings even after you turned it off has been fixed in the latest Cursor release. Update to the newest version and that should fully resolve it.

One note: if Grok is still set as the default from a previous switch, after updating, turn it off and pick your preferred model again. After that, it should stick.

Let me know if you run into it again.