Chat-window not shown - "Something went wrong"

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When opening a new or an existing chat window an error is occasionally shown with the message “Something went wrong”.

Copied error:
AgentPanel failed to render.

Error (Error): No Connect transport provider registered.

Stack:
at fYm.transport (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35612:99621)
at async ex.createSingleServer (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35612:102710)

Component stack:
at AgI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57959:126115)
at wJi (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57951:56784)
at div ()
at SgI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57959:123059)
at eOk (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57959:124818)
at div ()
at div ()
at BAA (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55729:4186)
at zxI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58929:70975)
at wJi (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57951:56784)
at vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58929:81597
at div ()
at YxI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58929:82053)
at tdI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57958:224230)
at VariantEnforcer (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:601:41290)
at div ()
at div ()
at VxI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58929:80735)
at F1k (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55719:90001)
at MPA (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55733:12420)
at LPA (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55733:10935)
at uix (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47095:39872)
at PgI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57959:185815)
at JCI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57970:276666)
at OCI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57970:275523)
at a1I (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57970:281784)
at oOg (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47098:68650)
at AlertDialogProvider (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:723:17311)
at ykk (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55704:289450)
at PortalProvider (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:612:8060)
at PortalLayeringProvider (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:612:8381)
at QxI (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58929:83008)

Steps to Reproduce

Open a new or an existing chat window - or the settings.

Expected Behavior

Content is shown - no error

Screenshots / Screen Recordings

cursor-error.png
cursor-error.png1271×790 20.3 KB

Operating System

Windows 10/11

Version Information

System info:
Version: 3.7.19 (user setup)
VS Code Extension API: 1.105.1
Commit: 80c653c2c3528e65016a0d304b54486084b470b0
Date: 2026-06-07T01:42:56.126Z
Layout: glass
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
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi Christian! Thanks for the full error text - that’s exactly what helps here.

This is a known issue we’re tracking. When it happens, the chat/agent panel’s backend isn’t ready in time as Cursor starts up, so the panel falls back to “Something went wrong” instead of loading. It’s intermittent and tied to startup timing.

The reliable workaround is to fully quit Cursor and relaunch - not just “Reload”. On Windows, close all Cursor windows and confirm it’s fully exited (check the system tray), then reopen. A fresh start almost always restores the panel; reloading tends to re-hit the same state.

Two things that would help us narrow it down:

  • Does a full quit + relaunch clear it each time, or does it keep happening on most launches?
  • If it’s on nearly every launch rather than occasional, endpoint security/antivirus scanning Cursor’s processes can delay startup enough to trigger this - worth checking with your IT team whether Cursor is allowlisted.

We’ve identified the root cause and it’s with our team.

8

Hi Mohit, thank you for your response and your support!

First of all, yes, when I fully quit and restart Cursor, the panel often shows up, but it can happen anytime again, when switching to another panel or even letting Cursor minimized in the background and maximizing it again.

Hitting the Reload-Button doesn’t help, as you said.

As you can imagine, it is a really annoying bug, so it would be great if you could fix it :slight_smile: