As many here, including Cursor devs, are aware, there is an issue with Cursor randomly deleting or changing files that it shouldn’t.
Today I lost several hours fighting this and due to „Restore checkpoint“ being too slow, which is a completely different topic, I resorted to Version Control and simply went back to the start of the day.
Anyway, to a avoid such issues (deleting and modifying files it shouldn’t) I propose a „lock file/folder“ function, which will signal to AI not to touch anything marked as locked.
The reason AI does change those files is context window that can’t possibly have the whole history of changes and touches files for which we already said „fine, looks good, let’s move on“. But due to its „fish-like“ memory Cursor does not know that.
This simple lock mechanism would mark certain portions of the codebase as done and cursor can avoid it. As long as we don’t „unlock“ it again.