I always thought Cursor kept an ongoing diff when it presented the “keep” lines (red and green highlights). I tend to not click on “Keep” right away as I like to keep around the more recent changes this way than the usual change indicators in the line gutters, and only when I’m happy with something do I “Keep” and commit it.
Anyway, I guess Cursor had a memory leak and next thing I know I’m presented with the Mac dialog telling me to kill some apps to free up memory. Cursor was eating up 58GB so I force-quit it and with it apparently the lines that I didn’t hit “Keep” on.
I haven’t encountered this before, should the IDE have presented a recovery diff on next load up?
Thankfully I remembered to use the VSCode/Cursor timeline feature which keeps track of changes periodically and was able to recover work. When I asked Cursor to recover the work it basically told me that it wasn’t possible (which obviously wasn’t the case, but maybe it doesn’t know the IDE context?). Maybe something Cursor agent can improve on is pointing users to that feature.