Request ID: 971784e7-9816-457c-9c15-f49a7dbb8266 An unexpected error occurred. [unavailable] PING timed out Mpe: [unavailable] PING timed out at yy1 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.de

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: 971784e7-9816-457c-9c15-f49a7dbb8266
An unexpected error occurred.
[unavailable] PING timed out
Mpe: [unavailable] PING timed out
at yy1 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35721:27577)
at hsg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35721:26306)
at Iy1 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35722:7469)
at wsg.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35722:12370)
at async Ble.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48122:2927)
at async yJg.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48193:12152)
at async yJg.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48193:20412)
at async Xct.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35852:1973)
at async IdI.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:57956:279675)
at async PDI.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:58989:20593)

Steps to Reproduce

Open Cursor IDE on MacOS system, open existing local project folder.
Select part of project source code, send AI chat request to ask code analysis & modification via Cursor built-in AI dialogue.
After waiting for several seconds, popup error alert: An unexpected error occurred, Request ID:971784e7-9816-457c-9c15-f49a7dbb8266, error root shows [unavailable] PING timed out.
Click Try again button multiple times, the identical error still recurs continuously and cannot normally get AI reply content.

Expected Behavior

After sending code-related query in Cursor chat panel, the backend agent connects normally without ping timeout, AI can receive request and return corresponding code analysis/answer content stably, no unexpected error popup.

Screenshots / Screen Recordings

1.jpg
1.jpg1590×228 23.2 KB

Operating System

MacOS

Version Information

Version: 3.7.12
VS Code Extension API: 1.105.1
Commit: b887a26c4f70bd8136bfffeda812b24194ec9ce0
Date: 2026-06-05T01:45:12.918Z
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: Darwin arm64 25.5.0

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hi @YaeSakura!

Typically, this error means the live connection between Cursor and our servers dropped mid-request (a keepalive ping didn’t get a response in time). Our backend did receive your request and retried it several times before surfacing the error, so this is likely a network connectivity issue on the path between your machine and our servers, not a problem with your account or the model.

If you’re facing this on all requests (if it doesn’t resolve on a new chat), I would suggest going to Cursor Settings > Network, running diagnostics (feel free to report back any failures), and also try changing compatibility mode to HTTP 1.1.

Switching networks / restarting any VPNs that might be play could also be helpful.

7

Thank you for your reply! I followed your suggestion to switch compatibility mode to HTTP 1.1 and ran the network diagnostics. The Cursor works properly now, thanks a lot for your help!