Problem Statement
Cursor’s frequent updates to system prompts (approximately monthly) create significant challenges for users with complex custom rule systems. While these updates benefit casual users, they can disrupt workflows for power users who have invested time in creating sophisticated multi-level rule systems.
For example, I’ve developed over 10 different rule files for various use cases, and each system prompt update requires substantial rework to maintain compatibility. This creates an unpredictable development environment where previously reliable functionality suddenly stops working.
Proposed Solution
I propose Cursor implement a “System Prompt Version Control” feature that would:
- Allow users to select a specific version of Cursor’s system prompt and lock it for stability
- Provide an option to override the default system prompt with a custom one
- Include clear documentation about changes between system prompt versions
This approach is similar to how Cursor already allows users to select different model versions, including older ones.
Benefits
For Users:
- Increased stability for complex workflows
- Reduced maintenance time spent fixing broken rule systems
- Greater predictability when developing custom rules
For Cursor:
- Improved user satisfaction, especially among power users
- Reduced support requests related to system prompt changes
- Ability to continue innovating system prompts without disrupting existing users
Request for Feedback
I would appreciate the Cursor team’s perspective on this issue. If my understanding of how system prompt changes affect custom rule systems is incorrect, I’d welcome clarification. Either way, this functionality would provide greater control and stability for advanced users while allowing Cursor to continue improving the default experience.