Cursor switchs to "Auto" instead of using the designated model

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I build a plan with a model eg. Gemini-3-pro.
When i click build plan, the model automatically switches to “Auto”.
It happens way to often to be a mistake. this happens in the latest version.

It’s really a violation of users’ trust. If I want to use a model then use that model, give me an error but don’t bloody switch the model because you want it so.
Perhaps there should be a setting that prevents automatic model switches.
If I want to run with “Auto” I’ll chose that option myself.
No wonder the code produced was rubbish.

Steps to Reproduce

Create a plan with Gemini and then try to “Build” it. The agent starts with “Auto” model.

Expected Behavior

The agent should be locked with the user designated model. If there’s a problem i expect an error not an automatic switch to “Auto”!

Operating System

MacOS

Version Information

Version: 2.4.30
VSCode Version: 1.105.1
Commit: 0f8217a84adf66daf250228a3ebf0da631d3c9b0
Date: 2026-02-06T23:20:57.191Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

“Gemini-3-pro-preview”, “Sonnet-4.6”

Additional Information

Don’t switch to “Auto” unless the user explicitly selected “Auto”. Who uses auto anyhow?

Does this stop you from using Cursor

Yes - Cursor is unusable

3 Likes
3

Hey, thanks for the report. This is a known issue. The model can actually switch back to Auto when building a plan.

So the team can check if this is the same bug or a regression, can you share the Request ID? You can find it in the chat context menu (three dots in the top right) > Copy Request ID.

Workaround: After you pick a model and click “Build plan”, double-check the model selector before the agent starts. If it switched to Auto, change it back manually.

A similar issue is described here: To-dos Selected Build in New Agent Not Using Selected Model to Build this Plan. They found that “Build in New Agent” uses the model from the last agent you ran, not the one selected in the plan. You might be seeing something similar.

Let me know if you find any pattern, like whether it happens every time or only in certain scenarios.

5

It’s possibly the same issue.
However the model for Build goes to “Auto” in my case. It happened in the latest version. This is super annoying. Indeed it can be fixed manually if you don’t get carried away. Clicky clicky.

Hope it gets fixed soon.
RequestID: 697302a6-e5a9-4232-9892-da5ef59e9ea4

1 Like
7

If this continues I might cancel my Cursor subscription, I keep getting dumb unusable results. I should have an option to never EVER use auto.

1 Like
9

Hey there!

This should be fixed as of the latest versions of 2.5.

10

Still happening for me on 2.5.20

1 Like
11

Have the same problem. Auto keeps failing on the same problem, switched to a stronger model to fixed the problem. After awhile, the same problem comes back.

After inspecting, notices the model magically switches back to Auto and fails back at the exact problem.

This is BS and time wasting. I choose auto when I want to.

I rather get rate limited on a stronger model, than switching to a weak model I knew it wasnt able to complete my task

12

I have the same problem here.

16

Still the same problem … can you fix that asap

17

Hey all!

The original issue in this thread was fixed in v2.5.

If you’re still facing an issue on v3.0.12+ (or whatever the latest version is, if you’re in the future!), please raise a new thread and fill out a complete bug report (including version and Request ID). Any steps that help us reproduce the issue are invaluable.