Feature request for product/service
Cursor IDE
Describe the request
Currently, Plans in Cursor are saved at the user level by default. I’d love an option to persist Plans within the project’s .cursor/ directory instead.
Plans turn out to be more useful than just a one-off thinking aid. In practice, they serve as:
- A record of past reasoning — I often revisit Plans to recall why certain decisions were made or what approach I was considering.
- Lightweight documentation — Plans naturally capture intent and context that formal docs often miss.
- A hierarchical planning structure — A high-level Plan can be broken down into smaller Tasks or Sub-plans, making it a practical tool for managing complex work.
Saving Plans at the project level would unlock several benefits:
- Portability — Plans travel with the project, so switching machines or onboarding a teammate doesn’t lose context.
- Version control — Plans can be committed to Git, making the evolution of project thinking traceable.
- Project isolation — Plans for different projects won’t mix together, keeping things clean and relevant.
Proposed behavior:
A setting (e.g. cursor.plans.storage: “project”) that, when enabled, reads and writes Plans to .cursor/plans/ (or a similar path) within the workspace root. The current user-level behavior would remain the default for backward compatibility.