experiencing frequent ‘agent stream can’t started, please reload window’ in recent days, after a cusor reboot today, all historical chats become unavailable(title still shows in agents panel but when click shows nothing), also I lost all user settings, which happens many times in the past, but lost historical chat is very very anoying, that’s context that I spend long time to build
Steps to Reproduce
as described in the bug
Expected Behavior
I want cursor have some reliable way to persist the chat history, like a local database or sth, do not let chat history lose randomly due to cursor crash, update etc, chat history is important asset.
Hey, thanks for the report. This is a known issue. The chats are still in the DB, but they don’t open because of DB issues. Your data is most likely not lost, the DB just can’t read it.
Try this:
Step 1: Check for corrupted files
Fully close Cursor (check Task Manager)
Open %APPDATA%\Cursor\User\globalStorage
Look for a file like state.vscdb.corrupted.1767... (the numbers will be different)
If you find one, rename the old state.vscdb as a backup, then rename the corrupted file to state.vscdb
Step 2: If there are no corrupted files
Can you share a screenshot of what’s inside globalStorage and workspaceStorage\[your-project]\? Sometimes the data is there. In a similar case, recovery via DM helped: Can't load or click on chats
About the “agent stream can’t started” error
This is usually related to Extension Host or network issues. If it happens often:
Try disabling extensions temporarily
Check if you have a proxy or firewall that might be blocking it
Important: This often happens when there’s not enough free disk space during an update, so the DB migration can’t finish properly. Please make sure you have enough free space before the next updates.
The team is aware of this issue and is working on a more reliable fix for chat persistence. Let me know if these steps don’t help and we can dig deeper.
do you have usual suspicion of what extension cause it? I am remoting in a cloud server through remote-SSH so I cannot disable all extensions like remote-SSH