# Plan mode executes on ambiguous phrasing; user meant "update plan" not "execute"

**URL:** <https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149>\
**Category:** Bug Reports\
**Tags:** composer, plan-mode\
**Created:** [March 9, 2026, 12:36pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149 "2026-03-09T12:36:50Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Baumgarten](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Paul\_Baumgarten](https://forum.cursor.com/u/Paul_Baumgarten)\
**Post date:** [March 9, 2026, 12:36pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/1 "2026-03-09T12:36:50Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

In Plan mode, I said “let’s use it” in response to a heading suggestion. I meant: add this heading to the plan document. The agent instead executed the full plan and made file changes.

I did not intend to execute. I expected Plan mode to block edits until I explicitly said something like “execute” or “go ahead.” I was surprised that edits were possible at all in Plan mode.

### Steps to Reproduce

Create a plan in Plan mode.  
Discuss a detail (e.g., a section heading) with the agent.  
Say something like “let’s use it” or “sounds good, use that” meaning “add this to the plan” or “update the plan.”  
Observe: agent executes the plan and modifies files instead of only updating the plan.

### Expected Behavior

Plan mode should require clearly explicit execution phrases (e.g., “execute the plan,” “go ahead,” “implement it”) before making edits.  
For ambiguous phrases like “let’s use it,” the agent should ask for clarification (e.g., “Do you want me to update the plan with this, or execute the plan now?”) instead of assuming execution.  
Alternatively: Plan mode could enforce read-only tool access so edits are blocked until the user explicitly approves via the Build button or similar.

### Operating System

Windows 10/11

### Version Information

Version: 2.6.11 (system setup)  
VSCode Version: 1.105.1  
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990  
Date: 2026-03-03T18:57:48.001Z  
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.22631

### For AI issues: which model did you use?

composer 1.5

### Additional Information

Related Reports  
System is making changes in Plan mode  
PLAN mode switches to AGENT mode without user input

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 9, 2026, 1:34pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/4 "2026-03-09T13:34:56Z")

</div>

Hey there!

What do you have configured under **Cursor Settings \> Agents \> Auto-Approved Mode Transitions**?

 ![Screenshot 2026-03-09 at 14.34.27](https://us1.discourse-cdn.com/cursor1/original/3X/f/4/f405f49b214d3140da4effdccb4ac2bb495050d1.png)

Unless `plan->agent` is included, you shouldn’t be automatically moved to Agent mode.

---

<div class="post-metadata">

**Author:** ![Paul\_Baumgarten](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Paul\_Baumgarten](https://forum.cursor.com/u/Paul_Baumgarten)\
**Post date:** [March 10, 2026, 1:37pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/6 "2026-03-10T13:37:57Z")

</div>

This is what I have:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/e/5e5dc11a33abe8a94d1a2b06f21998b58d674156.png)

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/6/0/60168ca7ecddc81aef71a67f6a0f4e377349d6e9.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 16, 2026, 8:16pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/7 "2026-03-16T20:16:13Z")

</div>

Thanks @Paul_Baumgarten

If it happens again, could you please share the [Request ID](https://cursor.com/help/troubleshooting/reporting-bugs#how-do-i-find-my-request-id) of the conversation? We’ve added some additional logging to help us figure out what’s going on.

---

<div class="post-metadata">

**Author:** ![Paul\_Baumgarten](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Paul\_Baumgarten](https://forum.cursor.com/u/Paul_Baumgarten)\
**Post date:** [March 28, 2026, 7:09am UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/8 "2026-03-28T07:09:32Z")

</div>

It happened again. Here’s the request id d1ba4e61-56d6-4dfd-a17b-cb25c6505498

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 30, 2026, 10:47am UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/10 "2026-03-30T10:47:27Z")

</div>

Thanks Paul!

Just to double check, are you seeing this before switching modes, or is the switch automatic?

 ![Screenshot 2026-03-30 at 12.46.46](https://us1.discourse-cdn.com/cursor1/original/3X/d/6/d6e22c5d2e06f0a126aef6361b092511f3462aed.png)

---

<div class="post-metadata">

**Author:** ![Paul\_Baumgarten](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Paul\_Baumgarten](https://forum.cursor.com/u/Paul_Baumgarten)\
**Post date:** [March 30, 2026, 11:49am UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/11 "2026-03-30T11:49:25Z")

</div>

No. I am not seeing that, the switch is automatic.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [April 1, 2026, 2:11pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/13 "2026-04-01T14:11:41Z")

</div>

Thanks @Paul_Baumgarten! I have not been able to reproduce this internally, but I’ve added your report to an internal ticket we use to track similar reports.

This shouldn’t be necessary, but if you run into this a lot, you might consider adding a User-level Rule to reinforce the proper behavior.

> [@Composer writing code in plan mode](https://forum.cursor.com/t/composer-writing-code-in-plan-mode/155838/3):
>
> Hey, thanks for the report and the request ID. This is a known issue. With Composer 2, Plan mode sometimes doesn’t stick and starts writing or applying code instead of planning. The team is aware. As a workaround, you can add a rule in .cursor/rules/: --- description: Plan mode safety alwaysApply: true --- CRITICAL: In PLAN mode, NEVER edit files or run commands. Only describe the plan. Wait for explicit user approval before any implementation. Not perfect, but it helps reduce how often it h…

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 30, 2026, 2:58pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/15 "2026-04-30T14:58:36Z")

</div>

Closed on April 30, 2026, 2:58pm UTC

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

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 14, 2026, 8:14pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/17 "2026-05-14T20:14:34Z")

</div>

Opened on May 14, 2026, 8:14pm UTC



---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 14, 2026, 8:15pm UTC](https://forum.cursor.com/t/plan-mode-executes-on-ambiguous-phrasing-user-meant-update-plan-not-execute/154149/18 "2026-05-14T20:15:06Z")

</div>

Hey @Paul_Baumgarten,  
The issue with plan mode executing on ambiguous phrasing has been addressed in a recent Cursor update. Updating to the latest version should resolve this. Let me know if you’re still running into it!
