Persistent Chat Connection Error On Pro+ Subscription

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

After getting the Pro+ subscription yesterday everything worked as expected and I worked for over three hours with no errors.

This morning however upon trying to continue the work session the agent could not connect. I opened a new agent and it was able to draft the plan upon various connection issues and now we are back to persistent connection error.

The cursor application is updated to the latest version. I have restarted cursor. I have changed HTTP and ran various Network Diagnostics tests. They always pass. Auto does not work, premium does not work, and individual models also do not work.

Please escalate this issue as this is extremly destructive to my operations.

Steps to Reproduce

By sending anything message or prompt. Agents and chats are simply not functional.

Expected Behavior

“Connection Error
Connection failed. Please try again, or contact support if the issue persists.
Copy Request (7da7db86-9c9a-481c-943c-f8a4d91ea8b7)”

Screenshots / Screen Recordings

cosur.bug.jpg
cosur.bug.jpg3012×1894 439 KB

Operating System

MacOS

Version Information

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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: Darwin arm64 25.2.0

For AI issues: which model did you use?

All of them

For AI issues: add Request ID with privacy disabled

Request ID: 7da7db86-9c9a-481c-943c-f8a4d91ea8b7
[unavailable] PING timed out
die: [unavailable] PING timed out
at e9A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34265:23755)
at Z5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34265:22658)
at a9A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34266:6285)
at Xou.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34266:10400)
at async qOa.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46830:10206)
at async b5u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46884:9277)
at async b5u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46884:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34327:17597)
at async _0a.acceptPlan (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34391:2387)
at async he (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47388:2555)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Chats now say “waiting for extension host” when I try to send a message

6

Hey, I see the screenshot and the error. This is a known client-side connection stall issue we’re tracking. The backend receives your requests fine, but the response stream drops on the way back to the client.

You mentioned you changed HTTP. Can you confirm you enabled Disable HTTP/2? Here are the steps:

  • Open App Settings Cmd+,
  • Search for HTTP/2
  • Enable Disable HTTP/2
  • Restart Cursor completely

If you already did that and it didn’t help, add this to your settings.json:

"cursor.general.disableHttp2": true

A couple quick questions:

  • Are you using a VPN or any proxy or firewall?
  • Is this a home network or a corporate or university network?

The team is aware of this issue type. Your report with the request ID and stack trace helps us prioritize. Let me know if the HTTP/2 toggle helps.

8

Okay so I ran the diagnostic with http/2 and i got an error only on ping this time -

Then I went in the actual settings and enabled disable HTTP/2

Cursor is now functioning again

1 Like
9

Thank you so much! very appreciated! @deanrie