Grok 4.7 reenables itself after being disabled in Settings

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Grok 4.7 keeps re-enabling itself after being explicitly disabled in the Models Settings

Steps to Reproduce

  1. Open Cursor Settings
  2. Go to list of Models
  3. Disable Grok 4.7
  4. Open a new Agent tab
  5. See Grok 4.7 re-enable itself

Expected Behavior

  1. Grok 4.7 remains disabled

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.7.27
VS Code Extension API: 1.105.1
Commit: e48ee6102a199492b0c9964699bf011886708ba0
Date: 2026-06-10T01:46:16.942Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.10
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 6.18.45-1-MANJARO

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey @Miguel_F, thanks for the report and the recordings.

Your version info shows Cursor 3.7.27, a build from June. New chats switching to a model you disabled (and turning it back on in Settings) was fixed in 3.14.7, so your install hasn’t picked that change up yet. The current Stable is 3.22.

On Linux, especially with an AUR or package-manager install, Cursor may not update itself. Please grab the latest build from Cursor · Download.

After updating:

  1. Open Cursor Settings > Agents > Conversation.
  2. Set “Default Model” to “Last Used”. This stops automatic model switching for new chats.
  3. In your open Agent tab, pick a non-Grok model in the model picker.
  4. Go to Settings > Models and turn off Grok 4.7 (and Grok 4.6 if you like).
  5. Open a new Agent tab a few times with Ctrl+N.