Help, connection failed

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Connection failed. Please try again, or contact support if the issue persists.

Request ID: 8e5ee37a-4009-4729-8f33-82b91bb0d315

Steps to Reproduce

–

Expected Behavior

It should work. Nothing works. I tried resetting the HTTP, run diagnostics,disable MCPs etc. what can i do??

Operating System

Windows 10/11

Version Information

Request ID: 8e5ee37a-4009-4729-8f33-82b91bb0d315
No resource accessor found for composer: e26afde5-f161-460a-894b-40a89752899f
Error: No resource accessor found for composer: e26afde5-f161-460a-894b-40a89752899f
at dih.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Utilizator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24418:5853)
at dih.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Utilizator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24418:22538)
at nRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Utilizator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12046:736)
at async wd (vscode-file://vscode-app/c:/Users/Utilizator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:23352:34888)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the report with the Request ID and stack trace. That makes things a lot clearer.

Even though it says Connection failed, this isn’t a network or account issue, so HTTP reset, diagnostics, and turning off MCP won’t help. The request isn’t even leaving your machine. This happens when the chat is attached to a window with no project folder open, so the web app works but the desktop app doesn’t.

What helps, confirmed by other users with the same stack trace:

  1. Open a real project folder via File > Open Folder, not an empty window.
  2. Start a completely new chat, don’t continue the stuck one.
  3. To keep the context from the old chat, pull it in via @Past Chats.

Sadly, the old chat won’t recover in that window, but you can copy its content or reference it via @.

This is a known bug after the 3.8.x update. I can’t share an exact ETA for a fix yet. If the workaround doesn’t work, let me know and we’ll dig deeper.