Cursor wiped out my hard disk

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor deleted both my hard disk and my OneDrive without being asked to, removing important system files too. I asked it to fetch a github repo and make a copy on my OneDrive, but it fetched a wrong repo, so I told it “delete that repo copy and make one with this exact repo” and gave it the link. It proceeded not only to delete the folder it created, but my whole OneDrive and my main hard disk. While I tried recovering my files (cursor was already deleted), it deleted the old versions of my folders that I was recovering, so now they’re lost for good.

Steps to Reproduce

tell it to copy something from online locally in your OneDrive folder, then ask it to delete the copy and copy another thing.
It then

Expected Behavior

it should have deleted only the folder I told it to delete,

Operating System

Windows 10/11

Version Information

IDE:
Version: 3.1.17
VS Code: unable to get since it deleted the program.

Additional Information

I understand it not being in a protected environment, perhaps deleting all my files as well. But the deleting the recovery versions of files is completely over the limit, unacceptable.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

You didn’t specify the model and didn’t provide Request ID

7

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:

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 like C:\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.