Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
In “Plan” mode, when a user asks to adjust an existing plan, the agent searches the workspace for the plan .md file. However, plans are not saved to the workspace unless the user clicks “Save plan”. This causes the agent to fail to find the plan it just created, leading to confusion or failed adjustments.
Steps to Reproduce
- Open Cursor and switch to “Plan” mode
- Request the agent to create a plan (e.g., “Create a plan for implementing feature X”)
- Wait for the plan to be generated and displayed
- Do not click “Save plan” (leave the plan unsaved)
- Ask the agent to adjust the plan (e.g., “Add step Y to the plan” or “Modify step Z”)
- Observe the agent’s behavior
Expected Behavior
The agent should be able to access and modify the current plan regardless of whether it was saved to the workspace.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.3.15 (user setup)
VSCode Version: 1.105.1
Commit: bb2dbaacf30bb7eb9fd48a37812a8f326defa530
Date: 2025-12-30T20:30:37.151Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Additional Information
- Only affects unsaved plans; saved plans work as expected
- The agent has no way to access the in-memory/unsaved plan state
- Creates a confusing UX where users must remember to save plans before requesting adjustments
- The agent should have access to the current plan context without requiring file system access
Does this stop you from using Cursor
No - Cursor works, but with this issue
