Connection issue - Agent, chat, nothing works

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It was working normal 2 days ago. I’m using vpn since past 6 months - Mullvad Vpn. I never faced such issue.

It happened after latest update today.

Steps to Reproduce

Chat logs:
[2026-01-27T08:23:58.718Z] Starting stream
[2026-01-27T08:24:01.583Z] Response: ‘foo’ in 2862ms
[2026-01-27T08:24:02.593Z] Response: ‘foo’ in 1010ms
[2026-01-27T08:24:03.587Z] Response: ‘foo’ in 994ms
[2026-01-27T08:24:04.583Z] Response: ‘foo’ in 996ms
[2026-01-27T08:24:05.585Z] Response: ‘foo’ in 1002ms
[2026-01-27T08:24:06.590Z] Result: Error: Streaming responses are being buffered by a proxy in your network environment

Agent logs:
[2026-01-27T08:24:02.080Z] Pushing next message
[2026-01-27T08:24:02.384Z] Response: ‘foo’ in 805ms
[2026-01-27T08:24:02.886Z] Pushing next message
[2026-01-27T08:24:03.201Z] Response: ‘foo’ in 817ms
[2026-01-27T08:24:03.702Z] Pushing next message
[2026-01-27T08:24:04.028Z] Response: ‘foo’ in 827ms
[2026-01-27T08:24:04.528Z] Pushing next message
[2026-01-27T08:24:04.842Z] Response: ‘foo’ in 814ms
[2026-01-27T08:24:04.842Z] Result: Error: Bidirectional streaming is not supported by the http2 proxy in your network environment

Screenshots / Screen Recordings

Screenshot 2026-01-27 at 2.05.28 PM.png
Screenshot 2026-01-27 at 2.05.28 PM.png986×1432 69.2 KB

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 24.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2.4.x version can't use agent behind company proxy
3

Hey, thanks for the report. I can see that after updating to 2.4.21, Chat and Agent start showing proxy buffering errors when using Mullvad VPN.

Try this workaround:

  1. Cursor Settings > search for “HTTP/2” > switch HTTP Compatibility Mode to HTTP/1.1
  2. Restart Cursor
  3. Run Network Diagnostics again

If it still doesn’t work, can you try testing without the VPN for a bit? That’ll help us tell if this is a change in Cursor or if Mullvad updated something.

Let me know if turning off HTTP/2 helps.

4

我也是，他妈的真是服了，经常升级，升级来升级去，却还是一坨答辩，我他妈怀疑就是故意浪费用户 Token 的