This is confusing. In newest version (i just purchased) i accept changes in the composer and they get saved directly. Sometimes i close files and it asks me to save or not, sometimes the message does not appear and files close immediately. Autosave is disabled. Anyway, closing and opening cursor again restores the last stage. Always. If files or projects are closed or not. So maybe i just misunderstood, but when changes are always somehow saved, what is the save function for anyway? Applying shouldn’t save. Or at least make it an option
Using newest sonet 3.5 2024
I noticed this too at one point and thought it odd but assumed it was an abberation. The difference between saving and accepting as I understand, is that saving is like a soft commit, accepting is a hard commit. Because Cursor will maintain checkpoint states for your code, if you save it, it makes it so you can run that code immediately in the dev build. However, it does not commit the changes to the actual code. It’s temporary.
That’s why you still see the red/green diff lines and hav the option to Accept based on what Composer/Chat proposes. Each proposal is like it’s own little basket of changes that you can “reapply” and test out. If you like it and the code works, then you finalize it by hitting Accept. That locks it in.
Worst case if you mess it up, I think you can ctrl+z sometimes but I don’t count on that.
Well, i tried vs code before and their approach is much more logical. Ai does changes, highlights them in red and green. Accepting them removes the differention and pastes the changes. You can copy the code, test it somewhere else, come back and safe or not. If you or the ai screw up at some point you can just close the file, dont safe, and open again and start where you started before. In cursor, i have to delete the folder and paste a backup with a different name, otherwise the timeline (and changes) applies even when the folder got deleted completely.