Connection failed up to now

Support Help
,
1

Connection failed. Please try again, or contact support if the issue persists.
Request ID: f297bf83-fedd-4d31-a2c2-a17549083c24
[unavailable]
RetriableError: [unavailable]
at yk1 (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:27652)
at Tag (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:26381)
at Ik1 (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:7469)
at Lag.run (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:12367)
at async zle.runAgentLoop (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48116:2927)
at async J$g.streamFromAgentBackend (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48187:13834)
at async J$g.getAgentStreamResponse (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48187:22596)
at async dut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35854:1970)
at async Object.io [as onSubmit] (vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47078:33305)
at async vscode-file://vscode-app/d:/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44977:103149

6

RetriableError: [unavailable] means Cursor couldn’t reach our AI backend on that request. It’s a transport-level connection drop, not an account or model issue. Because it’s retriable and most of your requests are going through, this is an intermittent network-path problem rather than an outage, so resending usually works.

When it keeps recurring, it’s usually a VPN, proxy, or restrictive network intermittently breaking the HTTP/2 stream the agent uses. A few things that help:

  1. Run Network Diagnostics (Cursor Settings > Network) to see whether API/Chat/Agent fail there.
  2. In the same Network settings, set HTTP Compatibility Mode to HTTP/1.1, then fully quit and relaunch (not just Reload Window). HTTP/1.1 routes more reliably through proxies and VPNs with no loss of functionality, just slightly higher latency.
  3. Update to the latest version. Recent releases include fixes for connection issues on restrictive networks.

More detail: Network, proxy, and remote connections.

If it still fails, are you on a VPN or proxy, and is it constant or occasional? Sharing your Network Diagnostics output would help us narrow it down.