Frequent “ConnectError: [internal] internal error” despite Network Diagnostics passing

[Lucas_Henrique_Diniz (Lucas Henrique Diniz Ostroski)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m consistently getting a connection failure when using Cursor’s AI features (Chat/Agent). The UI reports:

Request ID: 863fad84-498b-44af-8e2f-20c434b299bb
Error: ConnectError: [internal] internal error

It happens repeatedly, but Network Diagnostics shows everything as OK (DNS, HTTP/2, SSL, API, Ping, Chat, Agent, Marketplace).

Steps to Reproduce

Open Cursor on Windows.

Try to use Chat or Agent (send any prompt).

Error appears: ConnectError: [internal] internal error

Open Network Diagnostics → all checks pass.

Retry → error happens again.

Expected Behavior

Chat/Agent connects normally and returns a response.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (system setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

What I Already Tried:

• Changed HTTP Compatibility Mode:
  HTTP/2 → HTTP/1.1 → HTTP/1.0

Ran Network Diagnostics: everything passes.

–

Request ID: 863fad84-498b-44af-8e2f-20c434b299bb
ConnectError: [internal] internal error
at ezc.$endAiConnectTransportReportError (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12375:456006)
at kBo._doInvokeHandler (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22831)
at kBo._invokeHandler (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22573)
at kBo._receiveRequest (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:21335)
at kBo._receiveOneMessage (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:20152)
at GLt.value (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:18244)
at Ee._deliver (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at Ee.fire (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at xvt.fire (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12360:12156)
at MessagePort. (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15027:18433)

Does this stop you from using Cursor

Yes - Cursor is unusable

[Colin]

Hey @Lucas_Henrique_Diniz!

I looked up your Request ID and found an issue with one of our upstream services. I’ve reported this. Hope to have news for you soon. Sorry for the disruption.