2.0 - Plan mode not update plan.md

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Plan mode not update the current changes request from the chat.

Steps to Reproduce

Ask to built anything using plan mode. After the plan.md is created ask it again to update certain info.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.38 (user setup)
VSCode Version: 1.99.3
Commit: 3fa438a81d579067162dd8767025b788454e6f90
Date: 2025-10-29T20:45:40.883Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

gpt5-codex-mid

Does this stop you from using Cursor

No - Cursor works, but with this issue

+1 bug. I have the same problem.

Same here on a mac. It does not update the open plan, then if I ask it again, it overwrites the existing plan and looses the original plan. It will not save the plan to a disk file, so there is no way to recover.

Version: 2.0.43 (Universal)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 23.6.0

Same here, it will not update then plan, then when I ask again, it will overwrite the existing plan with the new changes. There is no way to save the plan.

@deanrie hi, can you report and fix this :squinting_face_with_tongue:

Hey, thanks for the report. This is a known issue the team is already working on.

Plan mode currently has sync problems:

  • Requests made after the initial plan creation don’t update the plan.md file
  • TODO lists don’t update correctly
  • Plans can be overwritten, losing the original version

Temporary workaround: some users keep plans in regular markdown files in their workspace instead of Plan mode’s internal system. Example: Plan mode save to workspace workaround

The team is working on improvements to Plan mode. I’ll add your report to help track impact. Thanks for the detailed repro steps.