Describe the Bug
On “Restore Checkpoint” action, Cursor rips files out of Staged Changes and reverts them to a prior state
Steps to Reproduce
Stage changes
“Restore checkpoint”
Boom! Your staged changes are ripped away and reverted to the checkpoint values.
Expected Behavior
Staged changes are inviolate. They are the user actively saying “This is the file state that I want to preserve.” You should not revert them from underneath the user.
Staged changes exists to perserve a file state so that it can be rolled back to a stable state. Preventing changes from being reverted from a Restore Checkpoint action is why they’re staged! Staged changes are a preliminary commit. You cannot take that away from users! It undermines the entire process for proving files work and staging them so they can be iterated against from a known good state.
If you HAVE to change the files, overlay the new values on top of the Staged Changes so that the Staged Changes remain, and a new Changes version is instanced.
That way the user can reject those changes to keep their previous Staged Changes.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.7 (user setup)
VSCode Version: 1.96.2
Commit: 7111807980fa9c93aedd455ffa44b682c0dc1350
Date: 2025-07-01T07:38:05.103Z
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.19044
Additional Information
Your “Current Cursor Version” instructions are for Mac. For Windows, it’s Help → About → Copy.
Does this stop you from using Cursor
No - Cursor works, but with this issue