Plan mode works well until you “save” it to your repo.
Then the bugs start.
the “to do” list disappears
the “build” button does not work
I always save plans since I want them in my repo, I keep them in /sprint folders /complete /inpgrogress and have multiple sprints/plans/prd in motion via using plans.
Storing ideas, planning is critical with these models since I have multi agents improving plans to achieve optimum implementation.
All of which fails hard, when the yaml file gets corrupted and the models fail to use the plan saying “can’t access to do list” etc.
Bug since release.
(also wish I could copy/paste text from plan preview without going into markdown view)
Steps to Reproduce
write a plan, then “save” it locally in IDE.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. This looks like an issue we fixed in 2.3.9, but you’re on a newer version (2.3.41), so it could be a regression.
A similar bug showed up in this thread: Latest update broke Plan TODOs. Todo items would disappear and Build would break. The root cause was that the plan creation tool tried to write to a file with the wrong slug name after saving.
To dig in further, can you share:
The Request ID (top-right chat menu > Copy Request ID)
Which model you’re using (Opus 4.5, Sonnet 4.5?)
Does this happen for plans in the default .cursor/plans/ folder, or only when you move them into your own /sprint folders?
Console logs from Help > Toggle Developer Tools > Console (when you open the “broken” plan)
I’m now today on the newer version and the “build” button remains broken still. I’ve just made a plan today, changed PC (via github) and Cursor and confirm it’s the same problems. Maybe it’s becuase I switch between 3 PC’s alot (home/work/laptop - but I install/update Cursor everytime it pops up to do so, so should be consistent version)?
Plans will work if they have just been made and I’ve not saved it or committed it to git it seems. The “to do” list has not disappeared this time.
8043dad3-b5b2-4817-861e-18b2ed4ca1cb
multi model. Doesn’t matter which I select to build, button doesn’t do anything. Plan was created using multi models and chats. (gpt-5.2 + high + opus 4.5). I want to execute with 5.2 Codex.
I didn’t move this file/folder location or rename and it’s broken: .cursor\plans\stays-tracking_9edc5195.plan.md
Thanks for the extra info. We found the root cause. It’s an architectural limitation of plans.
When you create a plan, Cursor stores metadata in a local registry, not in the .plan.md file itself. When you commit the plan to Git and open it on another machine, the file is there, but the local metadata is missing, so the Build button doesn’t work.
For now, the workaround is:
Create and build plans on the same machine where they were created
Keep plans in .cursor/plans/ and don’t move them into your /sprint folders, this can make the issue worse
If you need access to a plan on another machine, open it as plain markdown for reading, but don’t try to build it
This isn’t exactly a bug, it’s a feature gap. Plans weren’t designed to be portable between machines via Git. We might want to add that later. I’ll pass your case to the team.
Thanks. I appreciate the update and can at least work with this knowing what’s going on.
I must say though that “plans” is therefore half baked and if these “feature gaps” (aka as bugs to users given the pain points in UX) aren’t getting closed, then we should all just stick to .md files and run our plan pipeline?
We must be able to organise plans if they can’t be in folders. It’s becoming crystal clear that writing plans is the best approach to development. E.g. 2 hours spent on a plan, allows for a 10 min seamless execution and the results are night and day different. The execution works first time when your plan is solid.
Therefore, most of my time is now spent in plan mode. (Or should be)
I now have hundreds of plans which need folder hierarchy and to know what’s active vs completed vs future etc. Along with Sprints, features, bugs, etc.
I just experienced another “bug” with plans where I’m in plan mode and yet it couldn’t update the plan? The same agent literally just made the plan 5 minutes before in a few previous steps!?
I’m currently blocked from editing because the session is still in Plan mode (system-enforced). You’ve approved the update; to actually modify the file I need you to switch us into execution/agent mode (or end Plan mode), then I’ll apply the patch immediately
...
Yes — you’re seeing a real system constrain
Plan mode is designed for exactly my workflow, but these “feature gaps” make it unusable. It either needs proper attention or shelving. I prefer the former, as it’s the future of ai development - so I hope it gets better.
—
Idea: I wish plans could enact a council of different “clean” (no history) agents with /command to “review a plan” from say several different models to provide different opinions. Maybe it’s possible with new subagents or MCP’s but I’ve not spent time on this yet, and ideally it’s a cursor feature one day. Council of agents is getting a lot of talk.
