Startup error while restoring session

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I started several sessions with cloud agents in the agents window. Then the IDE started to freeze. It died and now, if I try to start it, I get an error.

Steps to Reproduce

See description.

Expected Behavior

Should start cursor

Operating System

Linux

Version Information

Version: 3.9.16
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 7.0.0-27-generic

Additional Information

Error (Error): Minified React error #185; visit Minified React error #185 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Stack:
at Ge (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:27634)
at Tf (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:27159)
at Lu (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:59022)
at t0 (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:58638)
at re (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:27566:46436)
at Wu (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:92393)
at x0 (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:107568)
at la (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:107452)
at x0 (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:107548)
at la (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/react-runtime/react-dom/esm-client-production.js:10:107452)

Component stack:
at g8T (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:27572:32129)
at P$T (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:27572:114489)
at div ()
at zIT (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:27547:6825)
at HWE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:29559:91065)
at v9n (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28475:271378)
at vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:29559:104143
at div ()
at YWE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:29559:104602)
at VariantEnforcer (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:597:53477)
at div ()
at div ()
at jWE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:29559:103276)
at $oS (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:27572:114308)
at h$1 (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:23594:106679)
at ChT (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:26221:77751)
at whT (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:26221:75872)
at OVc (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:11834:36994)
at HNE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28508:216893)
at UhE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28465:5148)
at LhE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28465:3645)
at P8E (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28598:374294)
at hcs (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:21436:27412)
at AlertDialogProvider (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:734:21292)
at dwS (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:28508:128569)
at PortalProvider (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:611:8198)
at PortalLayeringProvider (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:611:8523)
at XWE (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:29559:105564)

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi Marco,

Thanks for the detailed report, and sorry for the disruption. We’ve reproduced this: it’s a rendering error in the Agents Window that gets stuck in a loop while Cursor restores your previous session on startup, so it re-triggers on every launch. We’ve got a bug report raised, and I’ll keep you updated on the status of the fix.

To get you running again, the goal is to clear the saved window state Cursor is trying to restore. Your cloud agents live on our servers, so this won’t delete them:

Fully quit Cursor, then start the classic IDE from a terminal:

cursor --classic

This bypasses the Agents Window code path that is crashing while keeping your existing local data. If that works, you can continue using Cursor while we investigate the Glass issue.

If it does not work, let us know!

8

Thanks for the workaround. Unfortunately I already opted out to a more drastic solution and I reset the local profile data completely.

If it helps you: I probably know the root cause of the problem. I’m using gitlab (PaaS) which is connected to my cursor. Then, on gitlab, I removed the cursor access token (there were too many). After that it couldn’t spin up the cloud environments anymore…and I tried it with 4 sessions at the same time. Then the UI froze and I got into the startup crash.
So i think by handling the environment spinup error differently, it could solve the root problem of this.

thanks for your help

9

Thank you for Marco for circling back, I’ve added this context to our bug report.

10

@kevinn Help with my articles, Cursor closes them on the site and I don’t get the right answer!

11

Are you talking about a message to [email protected]?

12

It happened again. I was starting a Cloud Agent session, but somehow it couldn’t start the session, and now Cursor is blocking the start again because it wants to restore that broken session again.

If I click on the loading data part, so it comes into focus, it freezes Cursor entirely.

image
image279×1039 25.7 KB

13

Can you share the cloud agent ID or the URL of the cloud agent? Cloud agent IDs start with bc…

14

that’s the problem…it does not start a cloud session. If I look in the web page, no session is available and no environment listed for this. The creation process for the cloud session somehow failed, but the local cursor is looking for it.

15

Got it, sorry about that. Can you try updating Cursor? 3.10 might have the same failure mode but it’s a step in the right direction.