Can't load past chat after updating to a newer version

:white_check_mark: Checked the Forum

Yes – I reviewed this forum thread: Past chats stuck at “Loading chat…” after upgrading to 0.49.2.
It mentions the issue was fixed in version 0.49.3, but I am on version 0.49.4 and still experiencing the same problem.

:page_facing_up: Description

After updating to Cursor version 0.49.4 on Windows, I can no longer load chats that were created before the update. Chats created after the update load without issues.

This is a critical issue for me because I need access to past conversations for reference and ongoing work.

:counterclockwise_arrows_button: Steps to Reproduce

  1. Open Cursor (version 0.49.4) on Windows.
  2. Attempt to open a chat that was created before the update.
  3. Observe that the chat does not load (see screenshot).

:laptop: System Info

  • Operating System: Windows
  • Cursor Version: 0.49.4

:prohibited: Impact

Yes – this issue prevents me from accessing previous chats, which is essential for my workflow. I would appreciate a fix as soon as possible.

2 Likes

Hi, would be great to get some more detailed logs if you could do the following:

While in devtools, make sure to be in a fresh Cursor chat that loads properly, and then clear the console logs.

Then, switch over to one of these broken chats.

Finally, right click on the console, select “Save as”, and send that over. Can be in a private message!

@dcastl This is the log I got.

workbench.desktop.main.js:3091 [composer] No composer data handle found
handleDeselectingComposer @ workbench.desktop.main.js:3091
await in handleDeselectingComposer
(anonymous) @ workbench.desktop.main.js:47
GT @ workbench.desktop.main.js:47
s.value @ workbench.desktop.main.js:47
onChange @ workbench.desktop.main.js:3083
Na.defer @ workbench.desktop.main.js:74
(anonymous) @ workbench.desktop.main.js:60
Qa @ workbench.desktop.main.js:60
(anonymous) @ workbench.desktop.main.js:60
p8i @ workbench.desktop.main.js:62
pH @ workbench.desktop.main.js:62
pue @ workbench.desktop.main.js:62
sPn @ workbench.desktop.main.js:62
(anonymous) @ workbench.desktop.main.js:62
Hk @ workbench.desktop.main.js:62
tPn @ workbench.desktop.main.js:62
Hk @ workbench.desktop.main.js:62
cw @ workbench.desktop.main.js:60
r @ workbench.desktop.main.js:62
createComposerImpl @ workbench.desktop.main.js:3091
createComposer @ workbench.desktop.main.js:3091
(anonymous) @ workbench.desktop.main.js:47
GT @ workbench.desktop.main.js:47
s.value @ workbench.desktop.main.js:47
run @ workbench.desktop.main.js:3121
(anonymous) @ workbench.desktop.main.js:47
GT @ workbench.desktop.main.js:47
s.value @ workbench.desktop.main.js:47
handler @ workbench.desktop.main.js:50
invokeFunction @ workbench.desktop.main.js:3322
(anonymous) @ workbench.desktop.main.js:3050
GT @ workbench.desktop.main.js:47
n @ workbench.desktop.main.js:3050
executeCommand @ workbench.desktop.main.js:3050
(anonymous) @ workbench.desktop.main.js:598
await in (anonymous)
onChange @ workbench.desktop.main.js:598
Na.defer @ workbench.desktop.main.js:74
(anonymous) @ workbench.desktop.main.js:60
Qa @ workbench.desktop.main.js:60
(anonymous) @ workbench.desktop.main.js:60
p8i @ workbench.desktop.main.js:62
pH @ workbench.desktop.main.js:62
pue @ workbench.desktop.main.js:62
sPn @ workbench.desktop.main.js:62
(anonymous) @ workbench.desktop.main.js:62
Hk @ workbench.desktop.main.js:62
tPn @ workbench.desktop.main.js:62
Hk @ workbench.desktop.main.js:62
cw @ workbench.desktop.main.js:60
r @ workbench.desktop.main.js:62
openComposerImpl @ workbench.desktop.main.js:3091
await in openComposerImpl
openComposer @ workbench.desktop.main.js:3091
(anonymous) @ workbench.desktop.main.js:47
GT @ workbench.desktop.main.js:47
s.value @ workbench.desktop.main.js:47
v @ workbench.desktop.main.js:3099
(anonymous) @ workbench.desktop.main.js:3100

Same issue here on MacOS. However it happened after a normal System Reboot today, not when Updating Cursor. I had already updated Cursor yesterday to 0.49.4

Console Log also shows: “workbench.desktop.main.js:3091 [composer] No composer data handle found” (See attached logs)

Version: 0.49.4
VSCode Version: 1.96.2
Commit: ec408037b24566b11e6132c58bbe6ad27046eb90
Date: 2025-04-22T00:13:20.211Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

vscode-app-1745402981306.log.txt (3.5 KB)

Same issue here, it happened after a simple Cursor restart.

2025-04-23 20:28:10.796 [error] [composer] No loaded composer found: Error: [composer] No loaded composer found
    at get data (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:598:101515)
    at Xr.getComposerData (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:598:126395)
    at Hh.isComposerEmpty (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:971:7525)
    at Zh.handleDeselectingComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3091:1865) [composer] No loaded composer found
2025-04-23 20:28:16.125 [error] [canceled] This operation was aborted: ConnectError: [canceled] This operation was aborted
    at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2510:204519)
    at async Object.countTokens (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:97:15148)
    at async sui.updateTokenCount (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3168:4766) [canceled] This operation was aborted

Did anyone ever find a general fix? I think I just ran into this today: Auto-Logged Out on Restart, Now Chat History Won't Load After Logging Back in for Any Projects

I went digging in Cursor a bit deeper and I’m seeing the same errors generate (with my own file paths) as LorisFriedal in this window upon trying to load any past chat:

Tried troubleshooting this in Cursor itself – the Auto-agent response:


I’ve already tried 1 & 2. I just tried 3 (renaming the two cache folders mentioned there as _backup) and restarting – no dice. After opening Cursor in that directory and looking for fixes there, I can see old versions of files (probably for changelog/checkpoint storage) but none of the actual chats – so I’m not sure where that’s stored.

After digging through the various User folders to try to find backups with the Auto-Cursor-Agent (and/or figure out if my chat files are corrupted) it seems like that might not be something that’s surfaced through Cursor automatically:

Searching more here, a mod recommended a VS Code extension to try to recover chat history – so I guess that’s what I’ll try next: How to Recover Chat History from Cursor Files?

1 Like