Cursor agent CLI does not accept http/1.1

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

When trying to execute curser-agent inside WSL in windows, when connecting to corp VPN, getting connection error.
Same will work perfectly fine when not using VPN.

Steps to Reproduce

1)connect to corp VPN.
2) verify Cursor IDE connectivity is working fine (chat, agent, ping etc)
3) open new WSL terminal session and execute cursor-agent command.

Expected Behavior

cursor-agent should be able to “honor” the http/1.1 VPN proxy configuration and connect successfully.

Screenshots / Screen Recordings

Screenshot_156.png
Screenshot_156.png1919×1012 88.3 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45 (user setup)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Additional Information

Our corporation VPN does allow the connection to cursor. we have corporate license, and we have proxy configured and working in Cursor IDE with no issues. (we have http/2 disabled in the Cursor IDE settings.)
network diagnostics in Cursor IDE shows green V ticks in all tests:
DNS, SSL, API, Ping, Chat, Agent and Marketplace.
Please see attached screenshot, it has more details and showcase of the issue.

Does this stop you from using Cursor

Yes - Cursor is unusable

Cursor-CLI with HTTP/1.1
3

Hey, thanks for the report. Cursor CLI doesn’t support enterprise proxies yet.

4

Hey Dean, thanks a lot for the very quick response!
I know this might be a bit of a bold ask, but do you have any sense if/when support for enterprise proxies might be on the roadmap?

5

I don’t have that info yet.

1 Like
6

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