Grok set as default every time

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Grok is enabled by default upon opening the IDE on mac. I’ve disabled it. I usually work in auto mode. For someone who despises X and Elon, it’s infuriating to know that our credits are filling his pockets. Feels like you’re getting a back hander from them. Please fix.

Steps to Reproduce

Open cursor, there it is.

Operating System

MacOS

Version Information

Version: 3.16.29 (Universal)
VS Code Extension API: 1.128.0
Commit: 6246455961129c32969845e00aa25d87ae926ec0
Date: 2026-08-18T01:26:26.285Z
Layout: Agent Window
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.291
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Anything except for Grok

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. This shouldn’t happen with your settings, and it’s not something in your config.

To stop the model from switching when you open the IDE and in new chats, set the opt-out here:

Settings → Agents → Conversation → Default Model → “Last Used”

This makes Cursor keep the last model you picked instead of auto-switching on startup.

A couple of notes:

  • Disabling Grok in Settings → Models is respected, it shouldn’t switch to a disabled model.
  • Auto is a separate system. It picks a model for the task and can route to Grok too. If you want Grok fully out of your flow, it’s better to pin a specific model via “Last Used” and not rely on Auto.

Try “Last Used” and restart Cursor. Let me know if the setting sticks after restart, or if it switches back. If it switches back, send the Request ID right top chat menu > Copy Request ID, and we’ll dig in.

If you have questions about already billed usage, it’s best to email [email protected] since they can check your specific account.

7

Yes I’d done that but it seems to persistently revert to grok despite disabling it. Just checked and it has been re-enabled. Maybe was used as default after restart and when I went back to a project which had been using it, it re-enabled.

10

Title: New Agent chat via Ctrl+N ignores Auto and defaults to Grok 4.6

In the Agent window, Ctrl+N starts a new chat on Grok 4.6 (Grok 4.6 High Fast). Creating a new chat from the UI works: Auto stays selected.

Steps

  1. Open the Agent window.
  2. Set Default Model to Last Used (Settings → Agents → Conversation) and select Auto.
  3. Start a new chat from the UI → Auto is selected. ✓
  4. Start a new chat with Ctrl+N → the picker jumps to Grok 4.6. ✗

Expected Ctrl+N should use the same default as the UI (Auto / last used), not the recommended Grok 4.6 nudge.

Version: 3.17.8
VS Code Extension API: 1.128.0
Commit: 2fdd31c9f33f7fbe501f2d57772dc5bf64b63620
Date: 2026-08-20T02:18:12.724Z
Layout: Agent Window
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.291
OS: Linux x64 7.0.0-1011-oem

11

Hey, thanks for the detailed repro. Splitting it into UI button vs Ctrl+N really helps.

What you’re describing isn’t intended behavior. If Default Model is set to Last Used with Auto, a new chat created via Ctrl+N should behave the same as one created via the UI, and it shouldn’t jump to Grok 4.6. I’ve passed this to the team and we’re tracking it. I can’t share a timeline yet, but I’ll reply in the thread when there’s an update.

For now, a workaround is to create a new chat using the + button in the UI. Auto and Last Used are saved correctly there. If you want to fully remove Grok from your flow, you can also disable Grok in Settings → Models. After that, the switch shouldn’t move to it.

If Ctrl+N still switches to Grok after that, send the Request ID right top corner of the chat menu → Copy Request ID, and we’ll dig in deeper.