Cursor IDE
I upgraded to Cursor v2.3.35. I’ve held of running updates because Cursor has a history of breaking functionality. It looks like it has happened again. Plan mode will not create plan files anymore.
Reference id: 2b51b708-960f-4c39-afe4-612ac380df57
“Create plan failed to create/update plan file”
This is mildly frustrating as I’m running a demo of plan mode to work colleagues in a few hours.
upgrade to v2.3.35
switch to Plan mode
see Cursor not be able to create a plan file
Windows 10/11
Version: 2.3.35 (system setup)
Composer 1
2b51b708-960f-4c39-afe4-612ac380df57
Yes - Cursor is unusable
deanrie
January 16, 2026, 10:16am
3
Hey, thanks for the report. I see the screenshot with the error “Create plan failed to create/update plan file” and this is a known issue in recent 2,3.x builds.
Could you please share:
Developer Console logs: Help → Toggle Developer Tools → Console, reproduce the issue, then send a screenshot or paste the console output
Try switching to a different model (for example, GPT 5.2 Codex instead of Composer 1). This helped some users
Temporary workaround: until the bug is fixed, you can use the plan directly in the chat instead of creating an .md file. The functionality is the same, just without a separate file.
A similar issue was discussed here and was fixed in earlier versions: Plan mode seems to fail on final step of creating a plan . This might be a regression in 2.3.35.
Send the console logs and I’ll pass them to the team as a priority.
@deanrie thanks for the quick reply. While I appreciate your workarounds, they do create disruption which would be great to avoid via stable releases.
Attached is the console log.
cursor-plan-bug.txt (1.4 MB)
Changing models doesn’t resolve the issue.
It’s still not working
Version: 2.3.41 (system setup)
I have another presentation to colleagues on Cursor workflows in 16 hours. Would be great to be able to tell people Cursor is working again.
deanrie
January 20, 2026, 8:30am
7
Thanks for the info.
The team got your console logs from the previous post. This looks like a regression in 2.3.35+ that has affected a few users over the last few days.
For now, please try this:
Temporary workaround: roll back to 2.3.34:
After installing, turn off auto-updates: Settings > Application > Update > set it to “none”
This should restore Plan Mode until there’s a fix
If rolling back doesn’t help either, let me know and we’ll check other options.
Where are version downloads of Cursor?
deanrie
January 20, 2026, 8:53am
10
Here’s the link to the older version
After you install 2.3.34:
Go to Settings CMD + , > Application > Update
Set it to “none” instead of auto-updates
Restart Cursor
This should bring back Plan Mode until the regression fix lands. It’s a known issue and the team is working on a fix.
1 Like
Reverting to v2.3.34 didn’t work.
Request ID: c5f916e1-8d82-4b13-807b-2cd818362e64
deanrie
January 20, 2026, 5:24pm
14
It looks like this is a permissions issue in WSL:
Error: EACCES: permission denied, mkdir '/home/chris/.cursor/plans'
Try creating the directory manually in the WSL terminal:
mkdir -p ~/.cursor/plans
chmod 755 ~/.cursor/plans
After that, restart Cursor and check Plan mode again.
If it doesn’t help, check the directory owner:
ls -la ~/.cursor/
And share the output here so we can see if we need to fix permissions on the parent directory.
1 Like
That works! I’m back in business. I greatly appreciate your attention to detail and quick responses.
1 Like
Colin
February 4, 2026, 1:15pm
17
Hey @christhompsontldr !
This appears to be a bug in Cursor’s WSL permissions: it does not have permission to write to the home directory where we store plans by default. We’ve added a graceful fallback, so we now write to the workspace if the home directory is inaccessible, and this will come in 2.5.
Thanks again for the report.
1 Like
