[URGENT] Chat not working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Request ID: 02c69554-6bef-408e-b89e-687b24e2eac9
Connection stalled
LTe: Connection stalled
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4764)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)

Steps to Reproduce

Chat is not working for any model

Operating System

MacOS

Version Information

Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. I’m seeing the same stack trace from a few users over the last couple of days.

I’ll need a bit more info to diagnose:

  1. Network Diagnostics
    Cursor Settings > Network > Run Diagnostics. Please send a screenshot of the results.

  2. VPN/Firewall check
    Are you using a corporate VPN, Zscaler, McAfee, or anything similar?
    If yes, try disabling it temporarily and test again.

  3. Console errors
    Help > Toggle Developer Tools > Console. Please send a screenshot if you see any red errors.

Quick workarounds (while we’re looking into the root cause):

  • Disable HTTP/2: Settings > Network > HTTP/2 Compatibility Mode, or add this to settings.json:

    "cursor.general.disableHttp2": true

  • Corrupted index fix (if diagnostics are green): try renaming the project folder in Finder (for example Project → Project_v2) and reopen it in Cursor. This helped here.

Let me know what you find, especially the VPN info and the diagnostics results.

4

I have always used a VPN, which cannot be disabled. It was never an issue until today.

Diagnostic result (rest are fine)

image
image1122×848 53.3 KB

5

不仅是 Chat，是哪哪都不 working，我今天估计花了几百万 token，一件事都没干成，每次都是运行到一半中断，以前十次中错误两三次我忍了，但是今天的情况真特么太离谱了，而且中断这个问题从我第一天使用 crusor 开始就有，我真特么不知道 cursor 那些人整天在干嘛，还隔三岔五就升级，真是升级了个寂寞。。。

Not only the chat—nothing’s working anywhere! I’ve probably spent a few million tokens today and haven’t gotten a single thing done. Every time, it runs halfway and just gets interrupted. I used to put up with it when it failed two or three times out of ten, but today’s situation is seriously ■■■■■■■ ridiculous. And this interruption issue has been there since literally the first day I started using Cursor—I really ■■■■■■■ don’t know what those people at Cursor are doing all day. They keep rolling out updates every few days, but goddamn, those upgrades are totally pointless…

6

I see the screenshot, and yep, all endpoints are showing as [unavailable]. Thanks for running the diagnostics.

Try this workaround (it often helps with corporate VPNs):

  1. Cursor Settings > Network > switch to HTTP/2 Compatibility Mode
  2. Restart Cursor
  3. Run the diagnostics again

Also, please:

  • Go to Help > Toggle Developer Tools > Console and send a screenshot of any red errors, if there are any
  • Which VPN/firewall are you using exactly (Zscaler, McAfee, or something else)?

A similar case was recently fixed by an update: Connection Error (Unavailable), but you’re already on the latest version 2.4.21.

Let me know if the HTTP/2 workaround helps.

7

It has started working magically. Did not do anything now.
Please fix this folks, it is very irritating.