Switching models is unavailable in this conversation. Start a new conversation to use a different model,

Support Help
1

image
image192×104 6.06 KB

Why can’t I switch models in a new conversation after sending only one message?

3

I’m also facing this issue. I think it’s a useful feature and shouldn’t be removed.

4

Hey, thanks for the report.

I’ll need a bit more info to figure it out:

  1. What Cursor version are you on? Help > About Cursor > Copy
  2. Does this happen only in MAX mode, or in normal mode too?
  3. Can you reproduce it every time?
  4. Is the project local or cloud-based remote/SSH? Are you using worktrees?

For now, the workaround is to duplicate the chat (three dots in the chat menu > Fork Chat) and pick a different model in the copy. That keeps the context. Or start a new chat with Cmd+N or Ctrl+N.

5

1.Version: 3.0.16 (Universal)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0
2.normal
3.no
4.local;yes

6

Thanks for the info, but the screenshot shows the model is Opus 4.6 High. That’s the Opus variant with high reasoning, and it’s considered a reasoning model even if MAX mode isn’t enabled.

The model switch gets locked not because of MAX mode, but because Opus High generates reasoning traces that other models can’t pick up correctly. So the UI won’t let you switch mid chat even if you only sent one message, since the reasoning state is created on the first reply.

Options:

  1. If you need to switch models during the conversation, start the chat on Opus 4.6 without High, or on Auto or Sonnet, the switch works there
  2. If you specifically need Opus High, stay on it for the whole chat, or use Fork Chat to make a copy
  3. Start a new chat via Cmd+N and pick the model before your first message

Also, I’d update Cursor to the latest version: Help → Check for Updates. You’re on 3.0.16 right now, and newer builds might have improved the UX around the switch lock and the hint for why it’s disabled.

If you start on a non reasoning model and the switch still gets locked, that looks like a bug. Send a screenshot plus which model you’re switching from and to, and we can take a look.