Dozens of files created rapidly (about 1/sec) for a single Plan request, e.g.:
/home/$USER/.cursor/plans/m2_braintree_place_order_e115db91.plan.md
/home/$USER/.cursor/plans/m2_braintree_place_order_bb19eb13.plan.md
…many more
Impact
Disk bloat + noise; hard to find the latest plan.
Optional evidence to attach
here is a sample cmd + its result (254) that I jsut run:
ls -1 /home/$USER/.cursor/plans/braintree_place_order.plan.md 2>/dev/null | wc -l
254
Steps to Reproduce
Open Cursor, switch to Plan mode.
Ask for a plan for any non-trivial task (tested agains t model GPT 5.2).
Watch /home//.cursor/plans/ while the plan is being generated.
Observe many *.plan.md files created for the same name and dozens appear one after another as cursor tabs:.
Expected Behavior
One plan snapshot per explicit save, or a small bounded number per plan request.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Cursor 2.2.36 (plan Pro)
VSCode 1.105.1
Commit 55c9bc11e99cedd1fb93fbb7996abf779c583150
OS Linux x64 5.15.0-139-generic
For AI issues: which model did you use?
GPT 5.2
Additional Information
I’ve updated regularly in the last 2 weeks (from 2.2.20 onward) and that is happening since the last upgrade (2 days ago or so)
local project on ubuntu. the web project runs in a dockerized env (powered docker-compose) but cursor reads and writes only to the local filesystem (verified)
@deanrie don’t know it this can be a side-effect but I added s 20 bucks on demand this morning and in merely 6 hours work (not just coding today) they are gone. wonder if this problem causes gpt 5.2 to make much more api calls to openai due to the fact it seems redrafting the plan dozens or even hundred of times.
I’m on pro and I coded a lot this month hence I understand hitting the pro limits. but 20$ in just half a day looks a bit suspicious.
just for completeness’ sake, it does not seem rolling back to 2.2.35 is an option. I don’t see the possibility to select a 2.2.x specific version in the downloadable page. I can use an ‘old’ 2.2.23 AppImage that I’ve kept as a safe backup but no way to download a version that is not the “most recent”. Only possibility from the linked site is to download the most recent 2.1.x or 2.0.x or 1.7.x
It’s hilarious that every release introduces bugs previously non-existent in prior version, and the solution is to revert back “until the next update” is Cursor’s code for “until you’re forced to revert back again because of future release’s new bugs because we cannot stop with unnecessary updates and ignoring bugs as priority”.
Shouldn’t Cursor spend a couple week exclusively fixing bugs instead of unnecessary changes of UI or even new features? Doesn’t that sound like common sense?
Just fix all these bugs before you move forward with adding or switching sh*t around again?
Why even send new versions when in order to fix the new bugs you’d have to revert back?! Why doesn’t cursor actually work on FIXING BUGS and making sure things are stable before pushing new updates or adding futures or changing up the UI for the 10 time in a week?
Look, I understand that new changes can always add bugs, but when the bugs are from prior features that also didn’t exist in prior versions, and when it’s happening with nearly every single release, then the dev team - if they’re not all vibe-coding all of it, which really seems to be the case - is skipping a very fundamental concept in development !
Hello! When creating a plan, a large number of files are generated containing a sequential narrative of the plan with suffixes, which ultimately leads to the IDE crashing due to memory overflow. How can this be fixed?
Steps to Reproduce
switch to planning mode, write a request
Expected Behavior
One last file with the plan. Just like before.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
“until the next update” is Cursor’s code for “until you’re forced to revert back again because of future release’s new bugs because we cannot stop with unnecessary updates and ignoring bugs as priority”.