New chat always selects Grok 4.7

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When creating a new chat with your last selected model set to Grok 4.5, the new chat auto selects Grok 4.7 instead of keeping it on Grok 4.5

Steps to Reproduce

  1. Start a new chat
  2. Select Grok 4.5
  3. Write and submit a test prompt
  4. Start a new chat, selected model should show Grok 4.7 instead of Grok 4.5

Expected Behavior

When I start a new chat the model I selected from the previous chat (Grok 4.5) auto changes to Grok 4.7. This only happens when selecting Grok models.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.13.10 (system setup)
VS Code Extension API: 1.128.0
Commit: 4f02290ccd9304f0e6bf8ee85f6e9106f02ac1f0
Date: 2026-07-23T21:41:07.333Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @cjswayne, thanks for the report and the recording.

This is currently expected: when Default Model is set to “Cursor Default”, new chats that start from an older Grok model get moved to the newest one (Grok 4.7).

You can turn this off:

  1. Open Cursor Settings (Ctrl+Shift+J).
  2. Go to Agents → Conversation.
  3. Set Default Model to Last Used.
  4. Select Grok 4.5 in the model picker, then start a new chat.

Cursor staff’s explanation confirms that this is intentional when “Default Model” is set to “Cursor Default.” That intentional behavior is the problem.

A default that ignores my usage history and moves new agents to Cursor’s currently promoted model is not neutral. It steers model usage and can change cost, behavior, and output quality without the user choosing it. In my case, most of my agents use a different model, yet a new agent opened under a folder defaults to Grok 4.7 and initially will not let me change it. Requiring users to discover an opt-out setting makes this feel coercive.

Please change the default behavior to:

  1. Use the model that the majority of that user’s recent agents use, or at minimum the last-used model.
  2. Let the user explicitly pin a global default and optionally a workspace default.
  3. Never replace that preference because a newer or promoted model becomes available.
  4. Always keep the model selector editable before the first prompt is sent.

“Cursor Default” should be an explicit opt-in recommendation, not a mechanism for silently overriding the user’s established preference.

Cursor 3.21.9, Windows 11.