Agent mode change takes effect on running chat

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve noticed that if I executed a chat (e.g. write and edit A, B, C) with mode “Agent” then immediately buffered/queued by changing the mode to “Ask” or anything else (e.g. what is X now?) that the running chat start getting “Attempted Edit” with “Thinking” showing “We’re in Ask mode” or “We’re not in Agent mode, Switch…”.

Steps to Reproduce

  1. Use “Auto” for models (I didn’t test others, no quota).
  2. Request Create/Edit or any effect related to “Agent” mode only.
  3. Quickly switch change input to “Ask” and/or-not queue a question.
  4. See how current running chat will respond related to create/edit commands.

Expected Behavior

Current running chat to keep its “mode” related to its instance.

Operating System

Windows 10/11

Version Information

Version: 2.6.13 (user setup)
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

This may be more of a feature request. I agree this would be ideal to show in queue what each mode is, or at least if the mode changes from previous requests.

4

Hey, thanks for the report. This is a known issue. Mode switching is currently applied globally, not per turn, so the chat that’s already running also picks up the new mode.

The team is aware of this bug. There’s no timeline for a fix yet, but your report helps us prioritize it.

As a workaround, just wait for the current request to finish before switching modes. It’s not ideal, but it helps avoid “Attempted Edit” errors.

5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.