I’ve been working in the chat all day, and everything’s great. I’m working, working. Directly on the server. I’m sending everything to GIT as it should be. The cursor keeps changing 200 files, and my internet connection goes down. I click reconnect, and that’s it. There’s no chat. I don’t know where it left off. It doesn’t remember what I was doing. It’s like teaching someone something for a week, and then I go to the bathroom, come back, and say, “Who are you?” I’m shocked that no one seems upset by this. Why is this considered normal? This is insane. The cursor updates once a day, constantly, endlessly, but they don’t see this simple problem, and everyone’s happy with it. How is that possible?
2 Likes
hi @Vee and apologies for your chat history loss.
Our Engineering team investigated this issue and they found that it was caused by a rare condition related to the Agent Window feature, which is still in Beta.
For a small subset of users, there was an option to review the changes made by the Agent in an Agent Window, and when chosen, this inadvertently toggled the Agent Window feature on. By default, the Agent Window is enabled in the Cursor Settings > Beta > Agent Window toggle.
Unfortunately, because of this bug, chat history can’t be recovered. The good news is that a fix will be included in Cursor v1.8, which will make the feature more stable and prevent this from happening again.
We’re truly sorry for the frustration this may have caused and appreciate your understanding as we continue improving Cursor’s beta experience.
2 Likes
The Agent Window is no longer marked as beta, but I am still experiencing this history loss bug (or a related one). Any messages in the agent window are forgotten as soon as the window is closed. Let me file a ticket for the issue with some screenshots…
It is bad to lose chats, but are you genuinely going back to week old chats to continue submitting requests or is it just for your records? If you need the model to be “trained” for a week on your project with all of these chats, you should be having it create md files or some other documentation that you can place into any future chat to give it awareness, since creating new chats with fresh context is an important aspect to using these models.
I don’t think its like that at all, at least not on the week scale. Maybe the hour or day scale.
I may be wrong, but I don’t think having a week of archived chats makes new chats more aware of your project. Chats don’t build some shared context model behind the scenes, right? If it does, I should probably stop deleting all my chats lol. I think the reason tons of people aren’t complaining is because it doesn’t really affect them that much if they lose a ton of chats, just short term if they were still working in a chat that was lost, or long term if they need to keep records of all the requests. Unless of course your workflow was to hunt down week old chats and start working in them again.
Also you don’t have to update Cursor when it prompts and you can get opt out of the beta if you are in it which should reduce your updates drastically.
Also other people are reporting this too