I don’t see “Save to Workspace” anywhere (in the IDE window).
+1 for setting a default plans root. I also noticed the “Plan Viewer” only activates if the plan is within .cursor/plans - would like to see that regardless of root.
Hey, thanks for the bumps and extra details. I’ll split this into two topics since they got mixed together.
- Default storage location setting for @Stephen_Tunney, @Jeff_L, @gerbz
No update yet. The default ~/.cursor/plans is intentional, not an oversight, and there’s currently no separate setting like cursor.plans.storage: "project" to always create plans in the project automatically. I’ve shared your points portability, version control, and project isolation with the team as feedback. I can’t promise a timeline, but if there’s any update on the default behavior I’ll post it here.
This is separate from the feature request above. In remote environments like WSL and Dev Containers, the Save to Workspace option in the plan ... menu may not show up, even though it does on local Windows and macOS. The feature hasn’t been removed, this is a remote specific issue and we’re tracking it. There’s a dedicated thread here: Please bring back the "Save Plan to Workspace" feature
For now, the workaround is to manually copy the plan file from ~/.cursor/plans/ to <workspace>/.cursor/plans/. After that, the project will pick it up as usual.
@gerbz, can you confirm if you’re working locally or via WSL, Dev Container, or Remote SSH? If you’re local and it’s still missing, please share a screenshot of the open plan with the ... menu expanded top right, next to Build, and we’ll take a look. Note the option is only visible while the plan is still in your home directory. After saving it to the workspace it disappears, that’s expected.
Your note about Plan Viewer only activating when the plan is inside .cursor/plans is a separate point, I’ll pass that to the team too.
Let me know how it goes.
Remote SSH 
@deanrie
There could be a third issue here as well to work on:
Make Cursor Rules deterministic. These shouldn’t be treated like 
The Pirates Code where you can pick and choose when to enforce a rule. If that were the case they would be Guidelines 
Hey @gerbz, thanks for clarifying it’s Remote SSH. This is the same kind of remote-specific case as WSL and Dev Containers. The Save to Workspace item in the ... plan menu may not show up there, even though it does on local Windows and macOS. We’re tracking this and there’s a dedicated thread here: Please bring back the "Save Plan to Workspace" feature. It’s best to keep the discussion there so it doesn’t get mixed with the feature request about the default storage location.
For now, the workaround is the same: manually copy the plan file from ~/.cursor/plans/ to <workspace>/.cursor/plans/. After that, the project will pick it up as usual. I’ll also pass along the note about Plan Viewer only activating when the plan is inside .cursor/plans.
@Stephen_Tunney, on your third point about Rules being deterministic, I’ll be direct: right now rules are guidance for the model, not a strict contract, so they won’t give 100% enforcement by design. This isn’t something you can flip with a single setting. I’ll pass it on as feedback, but I can’t promise a change or a timeline. That’s also why the reliable path for plans is storing them in the project Save to Workspace or a separate default storage setting, not a rule instruction about the path.
On the main request in this thread, a setting like cursor.plans.storage: "project", there’s no update yet. If anything changes, I’ll post it here.
Hey @deanrie thanks for getting back to all of us here
I would suggest that the “Save Plan to Workspace” feature is moot and (human) error prone. Supporting Dev Containers, WSL2 (Remote SSH), WIndows, etc. are all far more complex for Cursor to support than a Cursor/workspace setting determining where plans are stored. Consolidate on one setting and save us Humans from ourselves over the long term Plans are specific to a repo or workspace and having those plans interleaved with others is a recipe for mixed/wasted contexts (i.e.. tokens).
Oh, also having plans saved to the workspace and allowing them to be checked into your source code control allows for others on your dev team to have the same context and known decisions shared so that everyone has the same understanding of the codebase they are working on.
If Rules are not deterministic, that’s fine but the Cursor ecosystem and how we Humans use it really relies on those Rules for so many workflows by design that I’m not quite sure why anyone would want any other behaviour from Rules.
Hey @Stephen_Tunney, you’re making a solid point, and I agree with the logic.
A single storage default instead of manually using Save to Workspace for each plan is really simpler and more reliable, especially given how many environments the manual approach has to cover (Dev Containers, WSL, Remote SSH). Your points about teamwork and keeping plans in version control also make sense. Shared context and documented decisions for the whole team is a strong case. I passed all of this to the team as feedback. There’s no update yet on adding cursor.plans.storage: "project", so I can’t share a timeline, but if anything changes I’ll post here.
On Rules, I’ll be direct again: right now they work as guidance for the model, not as a strict contract, so by design they can’t guarantee 100% enforcement. This isn’t something you can flip with a single setting. I passed that feedback along too, but I can’t promise a change or any timelines. That’s also why the reliable approach for plans is storing them in the project (Save to Workspace or a dedicated storage setting), not relying on a rule instruction about the path.
It’s best to keep the missing Save to Workspace in remote environments topic in a separate thread: Please bring back the "Save Plan to Workspace" feature so it doesn’t get mixed with the default storage request, and it’s easier to track separately.
Hey @deanrie any movement on this?
Hey @Stephen_Tunney, there’s still no update. On the default plan storage setting side cursor.plans.storage: "project", I don’t have anything new to share.
I don’t want to give you false hope. I shared your points with the team (team workflows, version control, project isolation), but there’s no priority or timeline for this setting right now, and I can’t promise it’ll happen. If anything changes about the default behavior, I’ll reply right here.
For now, the predictable workaround is the same: Save to Workspace for a specific plan. It moves the file to <workspace>/.cursor/plans/, and then it lives in the repo and gets committed to Git. For rules, I’ll say the same as before. By design they work as guidance for the model, not a strict contract, so you can’t reliably lock this behavior in via a rule.
One more thing. The missing Save to Workspace in remote environments like WSL, Dev Containers, and Remote SSH is better tracked in this thread so it stays separate from the default setting request: