Unified Proxy Support Across All Cursor Components

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Feature Request: Unified Proxy Support Across All Cursor Components

Platform: Linux (Ubuntu 26.04)
Cursor version: 3.18.9
Electron version: 40.10.3

Problem Description

Cursor appears to use different networking mechanisms for different components of the application.

When Cursor is launched with an HTTP proxy:

cursor --proxy-server=http://127.0.0.1:10808

Chromium-based components correctly use the specified proxy. However, some Node.js-based components (NodeService) appear to establish direct network connections, bypassing the configured proxy.

Setting standard proxy environment variables does not seem to resolve this issue:

HTTP_PROXY=http://127.0.0.1:10808
HTTPS_PROXY=http://127.0.0.1:10808
ALL_PROXY=http://127.0.0.1:10808

These variables are inherited by NodeService processes, but direct TCP connections to external hosts are still established.

As a result, different parts of Cursor use different network routes.

Why This Matters

This behavior creates problems for users who need to route all application traffic through a proxy.

When using the proxy, Chromium-based Cursor components use it correctly, but Node.js-based components bypass it.

Consequently, some Cursor functionality may fail or use a different network connection than intended.

Feature Request

Please consider implementing unified proxy handling across the entire Cursor application.

Ideally:

  1. A proxy configured in Cursor settings or through --proxy-server should apply to all network requests, regardless of whether they originate from Chromium, Node.js, extensions, background services, or other internal components.
  2. All internal services should use the same proxy configuration.
  3. Standard proxy environment variables (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, including lowercase variants) should be respected consistently.
  4. WebSocket, HTTP/2, gRPC, streaming connections, and other network protocols should also follow the configured proxy settings where technically supported.
  5. There should be a single, predictable way to configure proxy usage for the entire application.

Expected Result

When a user configures:

http://127.0.0.1:10808

all Cursor components should route their external network traffic through that proxy, without requiring separate configuration for Chromium and Node.js processes.

The goal is simple: one proxy configuration for the entire application, with no components silently bypassing it.

Operating System (if it applies)

Linux

6

Hey @Maxim_Annenkov,

This is timely! Cursor 3.28 (released this week) changed this. Cursor’s agent and background connections over HTTP/2 now go through your configured proxy too, not just the Chromium side. Please update to the latest version, then set the proxy in your settings rather than relying on the launch flag alone:

{
  "http.proxy": "http://127.0.0.1:10808",
  "http.proxySupport": "override"
}

Fully quit Cursor and reopen it (Reload Window isn’t enough).

Two things to know: the proxy needs to be an http:// or https:// proxy (SOCKS isn’t supported for these connections yet), and if you go the environment variable route, use HTTPS_PROXY / HTTP_PROXY rather than ALL_PROXY.

If you still see direct connections after updating, let us know which host they go to!