Connection Failed Bug

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: 08c1f483-33f1-4698-8d86-8919ddb5586b
WritableIterable is closed
gie: WritableIterable is closed
at h9A (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22875)
at w9A (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at rau.run (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async GOa.resume (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46834:13147)
at async _5u.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:9277)
at async _5u.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)

Steps to Reproduce

The error appeared after requesting some changes to the system under development.

Operating System

Windows 10/11

Version Information

Version: 2.6.21 (user setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report and the request ID.

This is a known server-side issue. The agent stream closes too early, which triggers the WritableIterable is closed error. The team is aware and already looking into it. No ETA yet, but it’s on our radar.

As a workaround, retrying the request usually helps. If it happens consistently, try:

  • Cursor Settings > Network > Run Diagnostics to check for any network issues on your side
  • If you’re using a VPN or a corporate proxy, try disabling HTTP/2: Settings > search HTTP/2 > turn on Disable HTTP/2

Let me know if it keeps happening and blocks your work.