Client stream abort Error

[codepower]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

workbench.desktop.main.js:44241 [composer] Client stream abort Error: submit_chat_abort_existing
at ALe.logClientStreamAbort (workbench.desktop.main.js:32182:25825)
at ALe.submitChatMaybeAbortCurrent (workbench.desktop.main.js:32181:58722)
at async Js (workbench.desktop.main.js:43415:4781) {arch: ‘x64’, platform: ‘win32’, channel: ‘stable’, client_version: ‘2.5.20’, error: {…}, …}
error @ workbench.desktop.main.js:44241
logClientStreamAbort @ workbench.desktop.main.js:32182
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:32181
await in submitChatMaybeAbortCurrent
Js @ workbench.desktop.main.js:43415
await in Js
callback @ workbench.desktop.main.js:43415
j6d @ workbench.desktop.main.js:453
（匿名） @ workbench.desktop.main.js:453
z6d @ workbench.desktop.main.js:453
zue @ workbench.desktop.main.js:453
update @ workbench.desktop.main.js:455
j6d @ workbench.desktop.main.js:453
Td @ workbench.desktop.main.js:453
a7b @ workbench.desktop.main.js:453
（匿名） @ workbench.desktop.main.js:453
workbench.desktop.main.js:44241 [composer] Client stream abort Error: abort_chat_and_wait_for_finish
at ALe.logClientStreamAbort (workbench.desktop.main.js:32182:25825)
at ALe.abortChatAndWaitForFinish (workbench.desktop.main.js:32184:4541)
at ALe.submitChatMaybeAbortCurrent (workbench.desktop.main.js:32182:10487)
at async Js (workbench.desktop.main.js:43415:4781) {arch: ‘x64’, platform: ‘win32’, channel: ‘stable’, client_version: ‘2.5.20’, error: {…}, …}

Steps to Reproduce

every hour

Operating System

Windows 10/11

Version Information

Version: 2.5.20 (system setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report and the detailed stack trace.

Here are a few things to try:

1. Disable HTTP/2: open app settings with Ctrl + , > search for “HTTP/2” > enable “Disable HTTP/2”. This fixes a lot of streaming issues, especially on some network setups.

2. Run network diagnostics: Cursor Settings > Network > Run Diagnostics. If you can, share the results here.

3. Are you using a VPN, a corporate proxy, or something like Zscaler? These often cause streaming disconnects.

4. Does this happen in all projects, or only in one specific project?

Also, next time the error happens, can you copy the Request ID? (Chat menu in the top right > Copy Request ID)

The team is aware of streaming interruption issues and they’re tracking it. Let me know how the steps above go.

[codepower]

Thank you. Here are my responses to each question:

1. I had already disabled HTTP/2.

2. The diagnostic results were all successful.

3. I am indeed using a VPN, but all my other web applications work fine.

This issue occurs in all projects.

Additionally, I found that when this problem occurs, simply executing the command “Developer: Reload Window” restores functionality until the problem recurs (perhaps after several tens of minutes).

I suspect there’s a problem with Cursor’s internal reconnection mechanism; it’s not actually resetting the connection.