How did a failed tool call to read files result in lost work? Are your old thread(s) still present? How many threads are lost? Did you change your workspace file location? I notice doing so loses your old chats . If that’s the issue, you can move the workspace file back to its original location and the chats should be back.
when I got to the frontend it had an error - compilation
so I asked other agent (I had worked before) to solve it
i dont know what caused the error, (maybe the agent who was working crashed all while working, or the agent i asked to solve it restaured to an ancient version)
but all changes from the last 15 days where lost (except from some design changes)
So no files were deleted? They just reverted back to a previous state? That sounds strange, if you weren’t using github for version control, which is how the models usually revert. I don’t know how it would revert without github.
So you lost some changes to some files, but not all files, and lost all your conversation history? I’d have to understand what happened before I could even try to suggest a fix. But tons of other people will know more than I will. You might try asking cursor directly at their support email: [email protected]
right - some changes lost
and about agent i only have todays conversation…
already sent mail to suport but i guess it will take a while to get an aswer
So you mostly lost old changes not related to the threads that still remain? It almost sounds like when those threads were lost, the work done in them was undone. But I don’t know how that could happen. Perhaps it has something to do with Cursor’s current troubles. They are reporting degraded services for agents. Maybe some of the damage is temporary. They might have their hands full at the moment fixing their own problems. I know this is not satisfying, but you need to establish effective version control policies/backups. 15 days without backups is suicide.
It means if you are missing chat threads, you aren’t alone. It could be a Cursor bug, not something unique on your end. Maybe they will fix it and restore your chat history, though from reading the thread there may have been data lost. I have all my old chats from what I see so the problem is not universal.
the sql db gets corrupted checksum during updates rendering chat history useless. run sql recovery on db file in cursor app data.
Also, the issue with file reversion is most likely from a undo/discard changes action in chat. A slight mis-click can erase all of agents work. Only fix manually going through chat history and copy and pasting changes from all edits in that tab. Git tracking will only cover committed files not agents progress.
the best course of action is manual copy and paste changes back into files. Otherwise copy all of chat and paste into new chat window. Optionally use spec story as a secondary chat db. you can extract all thinking and files changes from any chat session. paste in or have agent parse chat id for changes in that conversation.