Agent reporting in plan mode when chaining requests

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If you queue multiple requests where the first generate a plan in plan mode and but later requests are set to execute in agent mode I’m often getting the requests in agent mode requests stating they are in plan mode even when I’ve specifically switched to agent mode before adding the request to the queue. Other team members have also reported this and this is a recent issue (only seen it in the last few days). It also doesn’t happen every time.

Steps to Reproduce

Start a agent request in plan mode. Before completing send another request in plan mode to verify the plan or do some changes. This request is queued. Then send a request in agent mode to implement the plan (still before any previous steps have completed). This request is also queued. When the agent step is reached the agent reports that it is in plan mode and can’t make changes.

Expected Behavior

The agent step should be able to make changes as it was set to agent mode when it was queued.

Operating System

Windows 10/11

Version Information

Version: 2.6.22
VSCode Version: 1.105.1

For AI issues: which model did you use?

Opus 4.6 for plan, sometimes Sonnet 4.6 for follow up (still in plan mode), Composer 2 for agent

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. This is a known issue. If you queue requests with different modes plan → agent, the mode might not switch correctly for the next requests in the queue.

There are a few similar reports on the forum already:

The team is aware of this. Until it’s fixed, the workaround is to wait for the plan mode request to finish before sending the next one in agent mode, instead of queueing them at the same time.

Let me know if there’s anything else.