For one of my project (IOE-Agentic-Analytics-Platform) at location \wsl$\Ubuntu\home\mian
whenever the cursor is closed and restarted due to an update or just normally after exiting the app all my chat and Agent Mode history is completely deleted/disappeared from Cursor IDE. This always happen.
This is extremely disappointing and frustrating — a professional tool should not randomly erase essential user data after a system restart.
Please take this issue seriously as my ongoing work is hampered. and the cursor IDE becomes useless.
Steps to Reproduce
Work in Cursor IDE using Chat and Agent Mode
Restart the cursor or the computer. Open Cursor again.
Observe that all chat history and Agent Mode conversations are missing — the entire project history is gone.
Expected Behavior
Cursor IDE should retain all Chat and Agent Mode history after restarting the system.
User data should be safely stored and automatically synced, not permanently erased by a simple restart.
Note this happens only for this project. Majority of other project (not always but most of the times) chat history is not lost.
Weirdly enough, I was asked to login again and pass the Cursor tour onboarding when I opened cursor again (via cursor my.workspace in WSL2 / Windows 11).
When I was finally back, I could see my past chat history… but none of them will load. I am getting this (cf screenshot). See the “Loading Chat” ? It doesn’t go further than that. It never loads. This is super annoying.
And If I click in the “Show Chat History”, I get a “[composer] No composer data handler found” error
Steps to Reproduce
Update to Cursor 2.2.
Try loading a previous chat.
Expected Behavior
I should be able to load my previous chats without issue.
I was in the middle of a project and since the latest test run ended successfully and the “install update” button appeared very timely right at the end of the successful run, I thought “what the hell, let’s have a celebratory update”.
Since the latest update, my chat history won’t load. When I click the icon for the chat history I get this error in the lower left corner of the IDE: [composer] No composer data handle found
When I hit the PLUS button for a “New Chat”, I can see the titles of the earlier chats in the bottom, but I can’t view them.
Steps to Reproduce
Update Cursor to version 2.2.14
Open an earlier workspace with a chat history
Expected Behavior
You should see earlier chats but it’s stuck at “Loading Chat”.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
I need to have access to old chat logs to see what and how changes were made to my project for the test run to succeed. Right now I have a working project but I don’t know how to replicate the success because I lost access to the chats.
Same Here. For me, every latest update causes this problem. It doesn’t stop me from having a new chat, but it does frustrate me a lot when I cannot access any of my previous chats due to doing what Cursor wanted me to do by popping notifications to UPDATE.
another data loss bug. are you sure this is not unmaintained teenagerware we are paying for here?
i had a layout i liked. i updated cursor via the “update” dialog that appeared. cursor fukkkked around with the layout and now the panels are in a random order and my chat history (several open and --at least to me though clearly not to you – important chats) vanished. that’s a lot of work of mine you flushed because you don’t bother to test your changes. opus tells me there is no way to recover
Steps to Reproduce
update to 2.2.9. watch cursor fukkkk around with the layout and erase your chat histories.
Expected Behavior
what exactly do you think the correct behaviour is?
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
no i don’t need a workaround. no i am not sending you a screenshot of my company’s software. no, i don’t need a lecture about how to avoid this level of incompetence in the future. just test it yourself and fix it and add it to your minimal stash of regression tests so it doesn’t happen again. thank you
Hey all - we have 2 people working on this right now. Our understanding is that this is an older bug that is still appearing but with some frequency on update, so the more updates that occur the more likely you are to see it. We are working to fully rewrite all chat loading and finally fix this.
Hi all, I am working on our side to fix this problem.
I’m sorry about this situation. I can imagine how painful it might be to lose data, and we will fix this issue soon.
Today, we might have backup data available on the disk. The path is as follows:
C:\Users\USER_NAME\AppData\Roaming\Cursor\User\globalStorage\state.vscdb.backup on Windows
/Users/USER_NAME/Library/Application Support/Cursor/User/globalStorage/state.vscdb.backup on Mac OS
Please check if this file exists, when it was last updated, and try to replace the state.vscdb file without the .backup prefix with this one - it might help to recover some data partially.
And please copy the existing state.vscdb file somewhere first, if you already have new chats that you want to keep.
Thank you guys. I appreciate the acknowledgement of the importance of fixing this
Unfortunately, for me it’s toast… the backup file exists but given all my experiments, it seems that the “correct” backup file has been overwritten
So it is what it is, ■■■■ happens, but from now on, please please please change your upgrade strategy. Your serious customers want stable, super tested upgrades that they can rely on.
I don’t want to sweat of fear each time I push the “upgrade” button. And I am 100% fine not being able to enjoy ChatGPT 5.2 the day it is released if that’s the trade-off!
My 2cents advice: Put all your customers on a stable branch by default and only push the most tested and stable upgrades to those customers. Then, in Settings, allow those who want to always be at the very latest version of Cursor and experiment with all your new features as soon as they’re out to toggle “Experimental branch” and send them all the latest updates.
You could even mimic what Debian is doing with 3 branches:
stable for guys like me who only want the rock solid versions and are OK to wait a few months before getting the latest shiny new features.*
testing* for guys a bit more adventurous who are ok to encounter some minimal glitches here and there but are happy to enjoy the latest features within a few weeks after their release.*
unstable* for the crazy ones who want the absolute latest version and test new feature as soon as they are released.
Hey! Let me know if you got an email we sent over. We’ve been in an incident investigating and are adding major safety guardrails around chat loading that should be released tomorrow. I truly apologize, I understand the pain and we are working to fix this conclusively right now.
