When using HTTP/1.1 with two concurrent workspaces opened, the agent is highly likely to time out

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using HTTP/1.1 with two concurrent workspaces opened, the agent is highly likely to time out.

Steps to Reproduce

Use HTTP/1.1 mode, enable VPN proxy, and set the proxy connection port in the settings. Start the first agent then open the second workspace. The running agent would highly likely timeout.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (system setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

gemini 3.0 pro / gpt 5 high

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. Looks like network degradation when working with HTTP/1.1 + VPN proxy + two workspaces in parallel.

Could you please share:

  • Settings > Network > Run Diagnostics (full output)
  • Proxy type (HTTP/HTTPS/SOCKS5), VPN provider, are you using “Use system proxy” or manual setup
  • Request ID for timeout calls: chat menu (⋯) > Copy Request ID
  • Screenshot/text of error from DevTools Console Ctrl+Shift+I

Check:

  • Re-enable HTTP/2 (uncheck Disable HTTP/2) - does it reproduce?
  • Without VPN/proxy - does it reproduce?

Temporary workaround: don’t run the agent in two workspaces at the same time.

Please provide this data and I’ll pass it on to the team.

3

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.