Unable to access Chat History , despite all methods from forum

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

What I’m trying to do

Open an existing Agent/Chat thread from the sidebar (example title: “Mini missions card status…”).
What happens

The thread never loads; UI shows “Taking a little while…” indefinitely.

Steps to Reproduce

I simply closed my curor it had various folders on an unnamed workspace, idea was to refer the files for a migration, once the folder need was completed i removed them, only thing I last rememeber is closing the workspace, now when I open it , i can see my chat name avallable in side panel but the chat content shows a loop , an is tuck on loading.

Expected Behavior

From the sidepanel, if i can see the chat name , it should show me the chat content simpoly, without any issues

Screenshots / Screen Recordings

Screenshot 2026-04-13 172841.png
Screenshot 2026-04-13 172841.png2559×1246 295 KB

Operating System

Windows 10/11

Version Information

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Adding the console logs which seemed an issue:

workbench.desktop.main.js:65 ERR GlassWorkbench startup failed Error: Illegal argument: contextkey.setConstant(k, v) invoked with already set constant k
at Xw (workbench.desktop.main.js:28:2566)
at f0y (workbench.desktop.main.js:62:103875)
at new syc (workbench.desktop.main.js:58027:7431)
at Czd._createInstance (workbench.desktop.main.js:56604:2093)
at Czd.createInstance (workbench.desktop.main.js:56604:1522)
at workbench.desktop.main.js:60703:135987
at Czd.invokeFunction (workbench.desktop.main.js:56604:1028)
at QpS.startup (workbench.desktop.main.js:60703:135706)
at BvA.createWorkspaceForIdentifier (workbench.desktop.main.js:60760:5186)
at async pbS._createWorkspaceInstanceInternal (workbench.desktop.main.js:60759:51037)
at async pbS.ensureWorkspaceInstance (workbench.desktop.main.js:60759:49892)
error @ workbench.desktop.main.js:65
error @ workbench.desktop.main.js:65
error @ workbench.desktop.main.js:58042
startup @ workbench.desktop.main.js:60703
createWorkspaceForIdentifier @ workbench.desktop.main.js:60760
await in createWorkspaceForIdentifier
(anonymous) @ workbench.desktop.main.js:60760
_createWorkspaceInstanceInternal @ workbench.desktop.main.js:60759
createWorkspaceInstance @ workbench.desktop.main.js:60759
ensureWorkspaceInstance @ workbench.desktop.main.js:60759
createWorkspaceReference @ workbench.desktop.main.js:60759
(anonymous) @ workbench.desktop.main.js:44009
_updateDraftWorkspace @ workbench.desktop.main.js:44009
updateDraftHeader @ workbench.desktop.main.js:44009
updateDraftHeader @ workbench.desktop.main.js:60743
updateDraftHeader @ workbench.desktop.main.js:58042
(anonymous) @ workbench.desktop.main.js:60703
(anonymous) @ workbench.desktop.main.js:59733
(anonymous) @ workbench.desktop.main.js:59733
(anonymous) @ workbench.desktop.main.js:59728
Y3o @ workbench.desktop.main.js:44315
(anonymous) @ workbench.desktop.main.js:44315
Jg @ workbench.desktop.main.js:44315
S9 @ workbench.desktop.main.js:44315
bNn @ workbench.desktop.main.js:44316
Ekc @ workbench.desktop.main.js:44316

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, I can see the screenshot and the console logs. The GlassWorkbench startup failed error points to an issue initializing the Agents Window for this workspace.

Most likely the workspace state got corrupted after you deleted folders from the unnamed workspace. A few things to try:

  1. Reload Window: Ctrl+Shift+P then Reload Window. Sometimes you need to do this twice. We’ve seen this after updates and workspace changes.

  2. If that didn’t help, try switching to the Editor layout and then back to the Agents Window.

  3. If that still doesn’t work, try opening the project folder as a new workspace via File > Open Folder. Old chats are tied to a specific workspace, and if that unnamed workspace lost its folders, Glass may not be able to initialize its context correctly.

Unfortunately, if the workspace state is corrupted, some old threads may not be available in the UI. The chat data itself is still stored locally on disk.

Let me know if Reload Window helped or if you needed extra steps.

11

Hey @zapron24 quick update on this bug. We found the root cause, the GlassWorkbench crash due to double context key registration when the workspace switches to the EMPTY state after deleting folders. The fix is already merged.

You’re on 3.0.16. Please update Cursor to the latest version via Help > Check for Updates and see if your old chats open.

If the fix hasn’t reached your channel yet, the rollout is gradual, so it might take a day or two.

If the issue still happens after updating, reply here with the version you updated to and I’ll take a look.