Hey, thanks for the report. This is really critical, and I can see the screenshots with an empty desktop.
This is a known issue on Windows. The agent can run destructive shell commands like rmdir /s /q and Remove-Item -Recurse -Force via the terminal, and File-Deletion Protection and External-File Protection don’t protect against that because they only apply to built-in file tools, not terminal commands. We’ve seen similar cases:
Also, since you’re on a Russian Windows locale, there’s a chance another bug was involved, related to UTF-8 encoding in PowerShell scripts. That could turn a command meant to delete a specific folder into deleting the drive root. This specific bug was fixed in later versions.
What to do now:
- File recovery: as soon as possible, run Recuva or R-Studio. The key thing is don’t write anything new to that disk, so you don’t overwrite deleted data. The sooner you start, the better the chances.
- After you recover the system and reinstall Cursor, make sure to turn off Auto-run mode: Cursor Settings > Agents > turn off “Auto-run mode”. The agent will ask for confirmation before every terminal command.
To help track the incident, if you can:
- What exact Cursor version was it? Help > About
- Was Auto-run mode enabled?
- If you still have access to the Request ID from that chat, please send it (right top corner of the chat > Copy Request ID).
The team is aware of this issue. Let me know if you need help with anything else.