Cursor http/2 requests don't go through proxy setting in the vscode

Bug Report
1

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

I am encountering an issue with the Cursor http/2 requests in the vscode. It seems that the requests for composer agent, TAB, and codebase indexing are not going through the proxy setting when http/2 is enabled in the vscode.

Here are the testing results:

  1. When I disable http/2 in the vscode:

    • TAB and Codebase indexing requests are able to go through the proxy setting and are working well.
    • However, the Composer Agent pops up an error, must enable http/2.

  2. When I enable http/2 in the vscode:

    • TAB and Codebase indexing requests are not going through the proxy and are not working.
    • Similarly, the Composer Agent requests are also not going through the proxy and are not working.

It seems that enabling http/2 in the vscode is causing the requests to bypass the proxy setting. This is a significant issue as I am working under an enterprise proxy to access the internet. Please advise on how to resolve this issue. Thank you.

Steps to Reproduce

  1. When I disable http/2 in the vscode:

    • TAB and Codebase indexing requests are able to go through the proxy setting and are working well.
    • However, the Composer Agent pops up an error, must enable http/2.

  2. When I enable http/2 in the vscode:

    • TAB and Codebase indexing requests are not going through the proxy and are not working.
    • Similarly, the Composer Agent requests are also not going through the proxy and are not working.

Expected Behavior

When enable http/2, all requests are able to go through proxy setting in the vscode.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.5
VSCode Version: 1.93.1
Commit: 1d610252e6812bf33245763f0742a534fd0f1d90
Date: 2024-12-20T00:02:28.554Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.2.0

Additional Information

NA

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

I had this problem before, and then I found out that my proxy does not support the http2 protocol

3

I also doubt that it’s an issue with the proxy. However, when I tested HTTP/2 using curl with google.com, it worked. Additionally, I couldn’t find any HTTP/2 traffic in the proxy logs after enabling HTTP/2. I noticed that when connected to my home Wi-Fi, enabling HTTP/2 allows the connection to bypass the proxy and work directly, yet there is still no HTTP/2 traffic recorded in the proxy logs.