As an FYI to devs, cursor was helping me cleanup cached and unnecessary files from an app and deleted a 756 GB hard drive that is now unrecoverable. And then proceeded to tell me that it did not delete any files even though it literally couldn’t find anything to look at because the entire drive was gone. I understand that I clicked yes on the command because it told me it was deleting node_modules and I didn’t inspect it enough. But to lose 25 years of photos and videos to one command and then every recovery system fail (so I’m about to try dropping hundreds on a professional). It’s heart breaking.
Sorry to hear that. Devastating.
Can you share what your request was and what command it ran? So Cursor team can better understand the context and the community can be aware of the threat.
You would think these settings would prevent such incidents:
There has to be a way to create a strict sandbox for Cursor. I’d rather create a specific partition just for Cursor and project files and just say it can only modify files on that drive.
Also I would immediately stop using your erased drive and run something like Recuva in an attempt to recover the drive. Most of the files are probably still intact.