No response to prompts due to 'Internal Server Error'

Support Help
1

Request ID: f5090626-0ec8-45d5-a72d-08231727c7bb
[internal] Protocol error
RetriableError: [internal] Protocol error
at udf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9066:9690)
at Hqi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9066:8425)
at Scp (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:11962)
at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:16467)
at pdf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:5856)
at async fWo.runWithSharedTurnRunner (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9067:15819)
at async xV.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20459:3067)
at async aba.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:14009)
at async aba.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:23432)
at async jIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9229:2399)

Version: 3.10.17 (Universal)
VS Code Extension API: 1.125.0
Commit: c89f45b831621cdc5e951694db44fecd8fab1150
Date: 2026-07-05T06:39:45.228Z
Layout: IDE
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: Darwin arm64 25.5.0

4

Screenshot 2026-07-07 at 11.22.26 PM
Screenshot 2026-07-07 at 11.22.26 PM1686×402 32.3 KB

7

Hi @amrapali.srivastava Thank you for the forum post. The failure here is a “Protocol error,” meaning the connection carrying your request was interrupted or the response got corrupted in transit. We looked up that request ID and it never registered on our end, which points to the request being dropped on the network path between Cursor and our servers rather than a fault on our side.

Since this is network-level, the best steps to narrow it down:

  • Run Cursor Settings > Network > Run Diagnostics and review the results.
  • Test on a different network (like a personal hotspot) to see if it clears. This pattern often comes from a corporate proxy, VPN, firewall, or TLS-inspection tool interfering with the streaming (HTTP/2) connection.
  • Confirm Cursor’s domains are allowed through any proxy or firewall. Our guide covers the common fixes: Network, proxy, and remote connections | Cursor Docs
  • If it persists, reply with the diagnostics output and a fresh request ID and we’ll keep digging.

Since it sounds like you’re in a managed enterprise environment, it may also help to loop in your IT/network team, as proxy or firewall rules are a common cause.

8

Thanks Kevin. Turns out the latest cursor version is not working with the enterprise firewall. Changing HTTP compatibility from HTTP/2 to HTTP/1.1 worked for me.

10

Great! Thank you very much for circling back and confirming the fix.