Describe the Bug
When issuing a prompt that restructures or deletes files, Cursor correctly undoes edits (modified content) upon “revert,” but fails to restore any files that were deleted. This means that rolling back to a previous prompt leaves the workspace in an inconsistent state with missing files that cannot be recovered through Cursor’s undo/revert functionality.
Steps to Reproduce
1. In your project, issue a prompt to Cursor that causes it to delete one or more files (for example, “Move all utility functions into utils/ and remove the old files”).
2. Observe that Cursor deletes the specified files.
3. Immediately issue a “revert” (or “undo to previous prompt”) command.
4. Observe that:
• Modified files revert to their prior content.
• Deleted files remain permanently missing.
Expected Behavior
• All changes made by the prompt—including deletions—should be fully reversible.
• Reverting to a prior prompt should restore deleted files to their exact previous location and content.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.6
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:14:24.784Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Additional Information
Impact:
• Data Loss Risk: Users lose files outright when experimenting or iterating with restructuring prompts.
• Workflow Disruption: Forces manual recovery from version control or backups, negating the convenience of Cursor’s “revert” feature.
• Trust Erosion: Users may hesitate to use prompts that could delete files, limiting productive experimentation.
Does this stop you from using Cursor
No - Cursor works, but with this issue