Agent mode and model not always what they say they are

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using an agent the mode and model are not what set to what it says.
When on agent mode it asks me to put it in agent mode, and got a message that the model i was using was to busy and had to put it on ‘auto’, but it was already on auto.

Steps to Reproduce

I don’t really know.
I just seem to notice that the agent isn’t updating files, and just answers.
And the message about the model just popped up. no clue what happened there.

Expected Behavior

The settings for agent mode and model reflect what is actually set.

Operating System

Windows 10/11
Linux

Version Information

Version: 2.6.20 (system setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
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: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. We’re aware of both issues:

  1. Agent mode acting like Ask mode: this is a bug caused by a mismatch between the UI (shows Agent) and what actually gets sent to the model. Current workaround: if you notice the agent only replies and doesn’t edit files, try switching to Ask and back to Agent, or start a new chat.

  2. “Model too busy, switch to auto” even when auto is already selected: we’re tracking this one too.

The team is aware of both bugs. Your report helps us prioritize. For now, if it happens again, starting a new chat usually resets the state.

1 Like
8

To add to the workaround, i find that it also works to switch to ask mode and back to agent mode.
It seems to solve the issue for me at least.
The same goes for the model.

1 Like
11

Hey @controvi!

The agent mode and model display mismatch has been addressed in a recent Cursor update. Updating to the latest version should resolve this.

1 Like
12

I can say that i haven’t had the issue anymore since the update of 3.x