# Cursor unable to edit a plan **URL:** \ **Category:** Bug Reports\ **Tags:** plan-mode\ **Created:** [February 24, 2026, 3:04pm UTC](https://forum.cursor.com/t/cursor-unable-to-edit-a-plan/152815 "2026-02-24T15:04:45Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Urea](https://avatars.discourse-cdn.com/v4/letter/u/bc8723/32.png) [@Urea](https://forum.cursor.com/u/Urea)\ **Post date:** [March 1, 2026, 12:44am UTC](https://forum.cursor.com/t/cursor-unable-to-edit-a-plan/152815/7 "2026-03-01T00:44:44Z")
I am also experencing this issue. In plan mode, i created a plan for a proposed change, specificly i found a function call that was incorectly named so asked it to look for any others. it did, i pointed out some were obsolte code and can be ignored. instead of updating the plan, the agent acted to rewrite large portions of code, ignoring plan mode. i stoped and reverted it Telling it to update the plan, instead it created a readme doc listing things entirely differntly to the plan. Arguing the plan was not in workspace so cannot be edited. I beleive this relates to this thread also: > [@'Plan' mode is not respected by the Agent](https://forum.cursor.com/t/plan-mode-is-not-respected-by-the-agent/151802/3): > > Hola, Thanks for sharing this. What you’re seeing is basically the opposite: the agent behaves like it’s in Agent Mode and begins implementing without an explicit “ok, build now,” which defeats the point of Plan Mode and can cause unintended changes. ​ What to do until a fix lands While new Early Access updates roll out, you can reduce the damage by “pinning” stricter behavior using Rules: Add a global (User) rule in Cursor settings that clearly says: “If I’m in PLAN mode, do not edit files… --- _[View the full topic](https://forum.cursor.com/t/cursor-unable-to-edit-a-plan/152815)._