Plan mode - UX Feedback

Ideas Feedback
1

Hello there!

Love the product, been using it since release. Great work guys, genuinely game-changing.

I use Cursor at work and at home, and I use the Plan mode as a core aspect of my workflow. Each major feature starts as a plan, which I refine deeply before moving on to implementation. I’ve found a few user interactions difficult to manage, so I figured I’d jot them down here:

1 - Feature request: Configuration to save plans to .cursor/plans by default

Current Behavior

I’m sporadically unable to find the “Save to workspace” or similar button, I’ve seen it before, but am now reliably unable to find it in the context menus in the top right corner. This still isn’t the behavior I’d prefer, though.

Desired Behavior

I would benefit from a workspace-wide configuration to save all plans by default in .cursor/plans and have them ordered by date of creation. In the future, this could be an entire panel view and act as a proxy for Technical Design Documentation. I’d be glad to iterate further on this or build out a plugin.

Screenshot 2026-03-28 170731
Screenshot 2026-03-28 170731858×300 8.88 KB

2 - Potential Bug or UX misalignment: Plan mode loses track of task completion when running in another agent

Reliably seeing a disruption in task updates when running in a separate agent.

Reproduction:

  • Create a plan
  • Click on an individual task to execute, and execute in a new agent
  • Wait for completion
  • Tasks icon status isn’t updated in the original plan, and
  • When prompted, agent is able to recognize the mismatch in icon statuses when asked, but is unable to resolve it

3 - UX Suggestion: Make the todo header “Build in New Agent” button a multi-dropdown button that includes the standard “Build” button functionality

If this button were a multi-dropdown button, the user could select their default behavior, either standard “build”, which executes in the same agent window (the action executed by the “build” button in the nav / breadcrumb bar), or “build in new agent”.

Currently, the UX forces the user to know there are two buttons available to execute the same task differently.

new-agent

System / Version Details

Version: 2.6.21 (user setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

3

Hey, thanks for the detailed feedback, I can see the screenshots. On each point:

  1. Saving plans to the workspace by default

Right now plans are saved in the home directory, and Save to workspace moves them to .cursor/plans. The idea of a workspace-wide setting for auto-save is on our radar. For now, the Save to workspace button is available from the plan context menu (three dots at the top right of the plan panel). If it doesn’t show up reliably for you, let me know, that’s a separate issue.

  1. Task status doesn’t update when using Build in New Agent

We’ve had a few similar plan status bugs reported in recent versions. You’re on 2.6.21, can you check if an update is available? If you’re on the latest version and it still reproduces, please send the Request ID (three dots in the chat > Copy Request ID) and I’ll pass it to the team. The specific flow build individual todo in new agent then status not synced back might be its own case.

  1. Dropdown for Build / Build in New Agent

Good suggestion. I’ll share it with the team, it’s not obvious right now that there are two ways to start a build.

Let me know if issue 2 still happens after updating.