Feature request for product/service
Cursor IDE
Describe the request
Add support for multiple project contexts to help developers organize work across different tasks, branches, and topics.
Current Situation
Cursor currently uses a single shared chat context. While this works well for focused single-task work, developers often juggle multiple contexts simultaneously - working on feature development, fixing bugs, and planning refactorings in parallel.
Proposed Solution
Introduce “Projects” - isolated workspaces within Cursor, each with:
Separate Composer/Chat history
Independent @-file context
Optional metadata (git branch, issue number, tags)
Similar to Claude.ai’s “Projects” feature.
Use Cases
Parallel work: Maintain separate discussions for feature branch A, bug fix B, and refactoring planning C
Long-running discussions: Continue multi-day architecture conversations without losing context
Branch-specific work: One project per feature branch for clean separation
Benefits
Better context organization for complex workflows
AI maintains focused, relevant conversations per topic
Easy return to previous discussions
Reduced need to re-explain context when switching tasks
Implementation
MVP:
Project list in sidebar (create/rename/delete)
Project switcher (keyboard shortcut)
Isolated chat history per project
Project-specific @-files
Future enhancements:
Git branch integration
Project templates
Sharing/collaboration
Example workflow:
Developer works on “Refactoring: Repository Pattern”, switches to urgent “Bug #234”, then seamlessly returns to refactoring discussion - each maintaining its own focused context.