Describe the Bug
For the last few days I have been dealing with a nasty bug, where making any use of Cursor’s internal version tracking runs the risk of deleting files. These aren’t files that were created in the reverted chat, otherwise it would be expected behavior. I’ve seen it delete multiple files, often the same ones, but not always. If I revert to a previous checkpoint, and expect file A.cpp to be reverted to its previous state, it may end up reverting A.cpp correctly, but also deleting B.cpp and C.cpp in the process. I think at first it didn’t happen on every revert, but now it’s always happening.
Steps to Reproduce
- Make changes to the codebase using Agent (auto)
- Revert changes
Expected Behavior
- Only modified files should be affected by a revert, and the revert should simply revert to the previous state
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.3.0 (user setup)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:57:24.496Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631
Does this stop you from using Cursor
No - Cursor works, but with this issue