Cursor cannot work, help!

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: 5775de83-1b0d-49c7-b6fb-d68a1a3dd73e
An unexpected error occurred.
Canceled
RetriableError: Canceled
at wfa (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7547:81938)
at _cy (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:12878)
at Object.classify (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:17457)
at hcy (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:5856)
at async Lfa.run (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:16809)
at async age.runAgentLoop (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7681:34596)
at async f2l.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18743:14657)
at async f2l.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18743:32126)
at async Ije._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7660:2525)
at async Ije.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/twinc/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7651:74981)

Steps to Reproduce

Reinstall and relogin

Operating System

Windows 10/11

Version Information

Version: 3.16.17 (user setup)
VS Code Extension API: 1.128.0
Commit: 6b2afae0257df2bb5e1835f15165dc2f0de056b0
Date: 2026-08-14T01:41:12.803Z
Layout: Agent Window
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.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the report. For this Request ID, the request isn’t reaching our servers at all. We don’t see anything on our side, and there’s no service outage right now either. status.cursor.com is fully operational. This points to a network connection issue between your machine and Cursor. RetriableError: Canceled usually means the transport got cut off mid-way.

Let’s go step by step:

  1. Settings > Network > Run Diagnostics. Run it and paste the result here.
  2. Turn on HTTP/1.1 compatibility mode: Settings > Network > HTTP Compatibility Mode, or add "cursor.general.disableHttp2": true to your settings and restart Cursor. This often helps with VPNs, proxies, or corporate firewalls like Zscaler.
  3. Check your VPN, proxy, antivirus, or firewall with SSL inspection. Temporarily disable it and try a different network or a mobile hotspot.

Reinstalling won’t help here. It’s the network path, not the install. Let me know what the diagnostics show and whether step 2 helped, and we’ll take it from there.

6

That RetriableError: Canceled means the streaming request to the model backend is dying mid-flight — it’s almost always network-layer or a stuck client state, not your code. Since reinstall + relogin didn’t fix it, work down this list:

  1. Check the status page first — status.cursor.com. If there’s an incident, this error shows up en masse and no client fix helps. Your Request ID is exactly what staff need to trace it, so keep it.
  2. Switch models in the chat dropdown. If one backend route is broken, another model often streams fine — this also tells you whether it’s account/routing vs. local network.
  3. VPN / proxy / corporate network — these love killing long-lived SSE streams mid-response (Zscaler, SSL inspection, etc.). Test on a phone hotspot with VPN off.
  4. Fresh chat window. Your stack trace goes through submitChatMaybeAbortCurrent — a previous aborted request can leave the session wedged. New chat, new window (Agent → new tab), or reload window.
  5. Actual clean reinstall. The normal installer keeps user data. Kill Cursor, delete %APPDATA%\Cursor (back up your settings.json first), reinstall, log in.
  6. Still dying? Grab the full log from Help → Toggle Developer Tools → Console right when it errors — that has the real cause, and post it with the Request ID in this thread.

If it fails on the hotspot with cache wiped, it’s on their side — downgrade to the previous version or wait for the fix.