Same problem here. This happened already twice and costs me a lot of productivity and faith into you product. Pointing to an extension (spec story) is not the way to solve this issue. It is not hard to create local backups automatically. Instead of spitting out updates on a daily basis, better focus on the application core.
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I’m using cursor with WSL on windows and after the latest update
Version: 2.1.17 (user setup)
VSCode Version: 1.105.1
Commit: 6757269838ae9ac4caaa2be13f396fdfbcf1f9a0
Date: 2025-11-21T08:55:17.983Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
I cannot load my old chats, even after update cursor needed me to login again and everything was reset, what is happening??
Steps to Reproduce
Update to the latest 2.1.17 version.
congrats you are cooked.
Expected Behavior
old chats should comeup and I should not be forced to login again with everything reset
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.17 (user setup)
VSCode Version: 1.105.1
Commit: 6757269838ae9ac4caaa2be13f396fdfbcf1f9a0
Date: 2025-11-21T08:55:17.983Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Does this stop you from using Cursor
Yes - Cursor is unusable
1 Like
If I click on chat history I will get this error and the only way to open a new chat is the plus sign
Also my saved models and everything local got reset it seems, how can I just go back…
The old chats cannot be closed also
still no fixed after updata
版本: 2.1.19 (user setup)
提交: 1.105.1
日期: 39a966b4048ef6b8024b27d4812a50d88de29cc0
Electron: 2025-11-21T22:59:02.376Z
ElectronBuildId: 37.7.0
Chromium: undefined
Node.js: 138.0.7204.251
V8: 22.20.0
OS: 13.8.258.32-electron.0
Just updated with a new update:
Version: 2.1.19
VSCode Version: 1.105.1
Commit: 39a966b4048ef6b8024b27d4812a50d88de29cc0
Date: 2025-11-21T22:59:02.376Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.8-2-MANJARO
but still same problem. With chats older than yesterday (Version: 2.1.17). Chats from yesterday work.
Edit: I don’t understand how there’s an update almost every week about new ‘Agent capabilities’, etc. that may not be needed by every Cursor user but this seemingly basic requirement of prevention of lost chats (and thus lost data) seems to be an unsolved problem.
1 Like
Partial Solution for “Loading Chat” Issue
There’s a partial solution depending on the exact issue.
This can happen due to two issues:
A. You open Cursor from the folder rather than .code-workspace
This can be fixed easily. When you open a Cursor window, go to File > Save Workspace As and save it to a local folder (e.g., Desktop/Documents). Each time you open Cursor, open it from that .code-workspace file.
If you open from the folder, Cursor treats it as new and assigns a different workspace ID.
This is not related to a Cursor update.
B. Cursor rolls out a new update and you’re seeing the “Loading Chat” issue
This is the main cause of the “Loading Chat” issue.
When Cursor updates how the database/configuration works, old chats may become inaccessible.
If you’re using a Mac (not sure about Windows), Cursor keeps the local database (state.vscdb) for your workspace in:
Macintosh HD > Users > (your user) > Library > Application Support > Cursor > User > workspaceStorage > (ID of your workspace)
Inside this folder, you’ll have the database for your workspace, images (attachments) you upload to Cursor, etc.
For Issue A (opening via folder):
You can find the previous workspace ID here and migrate the chat info from that ID to the new workspace ID. This is straightforward if no Cursor update triggered the issue.
For Issue B (Cursor update):
You’ll need to try migrating the data from the previous ID to the new ID to see if it resolves the issue.
Important: Cursor stores many workspace-related files in this location. However, the actual messages you type and the Cursor agent types are stored in the cloud on Cursor’s side. If a Cursor update changes how the database is configured, the actual message content cannot be recovered from your side - this is a Cursor-side issue.
They likely clear excessive chat history periodically to reduce server storage.
If this is what happened, only the Cursor team can restore that chat history. Otherwise, if it’s an issue from your end, you can COPY my message and give it to an agent in Cursor (with appropriate system access), and the agent will review what’s going on and make the migration if needed.
It’s important to highlight to the agent that the workspace ID may have changed. The agent needs to analyse the IDs associated with your workspace historically to bring the data from different databases across the ID folders associated with your workspace/codebase.
I hope this is clear, and hope you are able to restore your chat history.
All the best
Marlon
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
After updating to Cursor 2.1.20, my chat history no longer loads. Version 2.1.19 was working perfectly on the same machine.
I’m not part of a team / org, just a normal solo user.
Environment
Cursor version: 2.1.20 (channel: stable)
Platform / OS: Windows 10 x64 (platform: win32, arch: x64)
Network: Normal home broadband, no VPN or corporate proxy in use
Summary of the issue
After updating to 2.1.20, existing chats are stuck on “Loading Chat” indefinitely.
I can ceate a new chat, so the AI is not completely dead, but:
Old conversations never load.
The chat area just sits there with the loading state.
The Developer Tools → Console shows repeated ConnectError entries with ERROR_UNAUTHORIZED on GetTeamCommands, even though I’m not in a team.
This did not happen in 2.1.19. The only change was the upgrade to 2.1.20.
Relevant console output
workbench.desktop.main.js:6880 [transport] Connect error in unary AI connect ConnectError: [unauthenticated] Error
at t (workbench.desktop.main.js:6330:409996)
at async Object.getTeamCommands (workbench.desktop.main.js:565:74406)
at async Rxo.loadTeamCommands (workbench.desktop.main.js:8975:2992)
Object
arch: “x64”
channel: “stable”
client_version: “2.1.20”
code: 16
errorDetails: [
{
type: “aiserver.v1.ErrorDetails”,
value: Uint8Array(82),
debug: {…}
}
]
errorDetailsDebug: “{"error":"ERROR_UNAUTHORIZED","details":{"title":"Unauthorized request.","detail":"You must be a team member to access team commands","isRetryable":false},"isExpected":true}”
errorMessage: undefined
errorName: “ConnectError”
method: “GetTeamCommands”
platform: “win32”
requestId: “not-found”
service: “aiserver.v1.DashboardService”
timeoutMs: “undefined”
[[Prototype]]: Object
workbench.desktop.main.js:8975 Failed to load team commands: ConnectError: [unauthenticated] Error
at t (workbench.desktop.main.js:6330:409996)
at async Object.getTeamCommands (workbench.desktop.main.js:565:74406)
at async Rxo.loadTeamCommands (workbench.desktop.main.js:8975:2992)
I also see related messages like:
[Background Composer] Error updating branch on git status change: Error: No full commit provider registered
[composer] Error checking git status for auto-accepting diffs: Error: No full commit provider registered
I suspect those are downstream effects of the AI / Dashboard service not initialising correctly.
Notes
This looks like a regression in 2.1.20 behaviour for solo users:
The client is calling aiserver.v1.DashboardService / GetTeamCommands
The backend returns ERROR_UNAUTHORIZED with “You must be a team member to access team commands”
That error appears to break the AI/chat initialisation, leaving chat history permanently stuck on “Loading Chat”.
In 2.1.19, chat history worked fine on this same setup.
If you need extra logs or a repro trace, I’m happy to provide more detail. Thanks!
Steps to Reproduce
Steps to reproduce
Start Cursor 2.1.20 (as a solo user, not a team member).
Open the Chat panel.
Click on any existing chat in the list (created before the 2.1.20 update).
Observe that:
The chat displays “Loading Chat” and never resolves.
Sometimes creating a brand-new chat works, but older chats remain inaccessible.
Open Help → Toggle Developer Tools → Console and watch the logs.
Expected Behavior
Expected behavior
Existing chats should load normally.
If team-related endpoints are not applicable (because I’m not in a team), the app should gracefully skip them rather than break chat initialisation.
Actual behavior
Existing chats are stuck on “Loading Chat” and never render.
Console shows repeated unauthenticated errors when trying to load team commands.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.20 (user setup)
VSCode Version: 1.105.1
Commit: a8d8905b06c8da1739af6f789efd59c28ac2a680
Date: 2025-11-22T14:51:59.472Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
For AI issues: which model did you use?
GPT-5.1 Codex
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Guys, FFS… I am having to revert back to 1.7 for the SECOND TIME after downloading 2.0 when it came out, saying oh hell naw, then going back to 1.7… waiting a while, and now downloading 2.1 only to be going back to 1.7 again. My last post got zero feedback from admins. Lost chats, chats retitling themselves, files closing, changes reverting (Reinstalling 1.7)
I repeat, I can’t see any of my prior chats dude. Whenever I download anything past 1.7 all my prior chats are wiped. THIS time around, it won’t even let me see a chat that I just created after I click off of it for the first time. I’m not posting a picture because there’s nothing to see. It’s the chat view with “Loading Chat” pulsing in the middle, and the chat selected that I just created. This is what was happening to any OLD chat I would click on prior to updating this time, but now ANY chat, old and new, are all biffed. I’m a paying user who would really love to be able to use the newer software and take advantage of the new stuff—but I can’t. So for that reason I’m going to say YES this keeps me from using Cursor, while I patiently wait for 2.x to deliver.
UPDATE: Now the same issue was happening last time that caused me to drop 2.0 completely, but now in 1.7. When I click on a chat, it just disappears that chat completely. Doesn’t archive it—it just goes away. Meaning, the app is unusable. Chats cannot be clicked because they disappear when clicked. I am going to uninstall and reinstall and see if that fixes it.
Steps to Reproduce
Uh, make a chat. Click off of it to another chat that DOESN’T load. Go back to chat you just made. Stare at “Loading Chat” for infinite amount of time.
Update: Select any chat—that chat disappears.
Expected Behavior
To be able to see the chat and use it.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.25 (user setup)
VSCode Version: 1.105.1
Commit: 7584ea888f7eb7bf76c9873a8f71b28f034a9820
Date: 2025-11-23T04:45:23.529Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Upon restarting Mac while Cursor is on, after restart that agent doesn’t load up
Steps to Reproduce
Restart Mac when a Cursor agent window is open
Expected Behavior
It’s supposed to load
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.77
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z (1 wk ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.1.0
Does this stop you from using Cursor
Yes - Cursor is unusable
Same for me! I cannot load any of the previous chat since updating to latest version today (2.1.26). I didn’t restarted my computer but just updated cursor as prompted. I tried to downgrade to previous version and it doesnt fix the issue….
This is getting silly now…its happened again…I didnt upgrade today, but I did restart my PC…..
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I cannot open my previous release agents (2 days ago), cursor holds on “Loading Chat”
Steps to Reproduce
Restart computer,
Restart Cursor
Agents panel
Clicking on previous on 2 days ago agents
Stay stuck on “Loading Chat” for a while.
New agent works.
Expected Behavior
Being able to open previous agents.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Since the latest 2 updates, previous release agents cannot be opened anymore
Version: 2.1.32 (user setup)
VSCode Version: 1.105.1
Commit: ef979b1b43d85eee2a274c25fd62d5502006e420
Date: 2025-11-25T05:00:12.749Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hi Marlon, thanks
But sorry, it’s not clear for me
Can you explain step by step how to fix and may be manage this migration of chat from previous version to new version manually ?
Thanks a lot!
Just to add to the bug, if you click on the chat that gets stuck on “Loading Chat”, you then cant click on working chat/s.
same
Same, That makes 3 days I’m stuck, have the top subscription with a pretty heavy on demand consumption…..
No support from 3 days and loosed my working time… No reply from support !!!
FIX IT or PROPOSE A WORK AROUND (even manual step by step approach) !!!
That should not be so difficult to propose a script to migrate old chats from sqllite db ……..
Otherwise, provide the structure of the chat history data stored locally, we will do that by ourselves.
Hi Eric
First you will need to diagnose the issue and figure out whether your situation falls under A or B scenario of my initial comment.
The best way you can do this is to copy my entire comment, open a new agent/chat in the Cursor IDE and paste it in the chat.
It will diagnose the issue based on my instructions.
clearly ask the agent:
Check if there are multiple workspace IDs associated with your workspace historically, if so ask the agent to migrate the past chats from previous IDS (which are separate folders stored in your system files in the OC).
Cursor agent will perform this automatically provided that you have given Cursor access to alter files outside of your working directory.
If the issue is simply a conflict with workspace IDs, it will resolve this issue, but if the issue is Cursor changed how the metadata stored in your local system, and they change the way they are stored, then you probably won’t be able to recover the actual chat content, because the actual chat content is stored in the cursor cloud.
Before you make any changes, make sure to ask Cursor to backup your current working directory and the system files where the local database of your workspace is stored in your local PC. This will prevent any error being executed by cursor agent.
Make sure to copy this response and give it to the same agent you’ve given my initial response. It will diagnose and explain to you what has happened exactly.
if you encounter any bottlenecks, reply here.
Cheers
Marlon
2 Likes