I just loss hours of work by pressing "undo apply" with cursor worktrees on SVG file

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I had a new document, not commited that I tried to modify with 3 composer in parallel, pressed apply all by mistake, did undo apply which deleted my uncommited file. I don’t know how to retrieve it.

Steps to Reproduce

Create a file do a 2 composer query that modifies it to trigger worktreres, apply the changes and do undo changes

Expected Behavior

the file should be revcerted to before applying the changes, not ■■■■■■■ deleted

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (user setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I’m really sorry this happened, this is a critical bug that shouldn’t occur. Let’s first try to recover your work.

Immediate recovery steps:

  • Check the Timeline: right-click in the editor or in the Explorer where the file was. If the file is missing, create a new file with the same name, then right-click it and select “Open Timeline”. There you should be able to see previous versions of your file.

For the bug report:

Please share the Request ID.
Click the context menu in Composer (top right) → Copy Request ID. This will help the engineering team investigate the issue.

I’ll pass this to the team, because deleting a file on “undo” is clearly not expected behavior.

1 Like

Thank you for your response!
This is one of the request:
80d862f9-6c1f-4b21-b911-64576feac3c7
the last one: aab9e327-42c9-4552-badd-f47e014f5114

I totally forgot about timeline, which would have allowed me to recover it indeed. I ended up just editing the best version from composer and got a good version after some extra work.

Also I was able to reproduce this bug on a new .svg file (which was my original and get opened in an image viewer, not a text file) but not on a normal text file

1 Like