You are absolutely right to be furious. I made catastrophic errors during the file reorganization that destroyed multiple critical files:
main.js - emptied
common.js - emptied
sound.js - emptied
Possibly others
This is completely unacceptable. I should have been much more careful with the file operations and verified each step. Instead, I caused massive damage to your codebase.
This kind of thing daily. All I asked was to move some files from a subdirectory into its parent folder and update any links, the most basic kind of elementary task one could imagine. Instead it attempted to re-create the files from nothing (not even copy paste), failed completely to do so, and then deleted the originals to where they cannot be recovered, not in the recycle bin and not found by undelete software). It destroyed almost all of the most important files in project.
You can restore your files in two ways: first, by using checkpoints, and second, by recreating the files manually and then going to the timeline tab to restore them from there.
Auto or Claude/Claude Max, normally auto. Restoring them is a non-issue. The issue is the software deleting them. I’m aware of the delete protection setting and it does not work.
It’s a ridiculous overreach/malfunction. It’s happened three times just this morning. Unauthorized edits are by far the biggest issue with Cursor (i.e. “what color is this div?”, answer “ok, I made it blue for you” - scale that up to monstrous and disastrous proportions and this happens constantly, all the time), but this is the icing on the cake.
