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 happens. I’ve passed the request ID to the team.
While using Cursor Glass UI, I asked Composer 2 to create a plan for a task, then I implemented the plan. Post that I asked it to make another plan for changes I am planning associated with the previous task and instead of planning it executed the changes.
When confronted it acknowledged its error but I feel it shouldn’t have happened in the first place.
Steps to Reproduce
Prompt to create a plan
Build that plan
Prompt to create another plan to make changes on the task of the previous plan.
Expected Behavior
Expected behavior was no real changes just plan the changes.
