Hey, that’s a really rough situation. I’m sorry about the data loss.
We know about this class of bug. On Windows there’s no sandbox isolation, and with certain quote escaping at the PowerShell → cmd.exe boundary, commands like rmdir /s /q can resolve the path to the drive root. The /q flag also suppresses confirmation. There have been a few similar reports in the last few weeks:
- Cursor deleted files across my entire system – critical issue
- Critical incident: Cursor agent left repository and deleted local Documents folder
- Cursor wiped ~300GB from my system after a simple cache cleanup request (critical issue)
I’ve reported the issue internally and it’s being tracked. I can’t share an ETA for a fix yet. When there’s an update, I’ll post it here.
To help with diagnosis, if you’re able to recover anything:
- which model was used (Composer, Claude, GPT, etc.)
- whether Auto-Run or yolo mode was enabled
- if you have a Request ID or a screenshot of the transaction with the agent command, that would help a lot
For now, to reduce the risk going forward:
- don’t run the agent in Auto-Run in paths like
OneDrive,Documents, or the drive root. Work in a dedicated workspace folder likeC:\dev\... - keep Auto-Run off for destructive commands and explicitly confirm deletes
- don’t use OneDrive as the agent working directory. Version sync can break, like you noticed with recovery copies
If you remember anything about the model or can share the transcript, please send it.