How to Set Up a Proxy in VS Code: http.proxy, Extensions and the Terminal

What a proxy does not change

This article is about network setup. If you use an AI extension in VS Code, such as GitHub Copilot, the service's own terms and its regional availability stay the same. GitHub's trade-controls page says users in sanctioned regions must still follow U.S. trade rules, that access differs by region, and that it is the user's own responsibility to comply. A proxy does not make a service available where it is not and does not change its terms.

• Sources:
• GitHub: GitHub and trade controls

Three words explained

A proxy is another computer that sends your requests to the internet for you; websites then see the proxy's address instead of yours.

HOST and PORT are the address of that computer and the number of its door. USERNAME and PASSWORD prove that you may use it.

An extension is a small add-on installed in VS Code. Many of them, including AI coding helpers, open their own internet connections.

How VS Code finds its proxy

The VS Code documentation says VS Code has exactly the same proxy support as Google Chromium: proxy settings are usually picked up from the system automatically, and the start-up arguments --proxy-server, --proxy-pac-url and --no-proxy-server can override them. For the editor itself, look first at the proxy settings of your operating system.

The same page says extensions do not yet get the same proxy support, and that http.proxy, http.proxyStrictSSL and http.proxyAuthorization are still part of the settings but are respected only in two scenarios. The sentence I read does not name them, so do not assume the setting works until the check below confirms it.

• Sources:
• Visual Studio Code docs: Network Connections

Where to set http.proxy

Open Settings (File → Preferences → Settings). In the left panel click Application, then Proxy. In the Proxy field type the address of your proxy, for example http://HOST:PORT. GitHub's Copilot documentation describes exactly this path and a Proxy Strict SSL checkbox next to the field; leave that box ticked. Then close VS Code completely and open it again.

• Sources:
• GitHub Docs: Configuring network settings for GitHub Copilot

Where to set http.proxy: example

{
  "http.proxy": "http://USERNAME:PASSWORD@HOST:PORT"
}

The same setting as it looks in settings.json. Replace HOST, PORT, USERNAME and PASSWORD with the values from My assets. The documents I read do not show the name http.proxy next to the Proxy field, so check in the Settings editor that the field you filled in is the one for this setting.

Username and password: in the address or in a prompt

Option 1, in the address. GitHub's Copilot documentation says Copilot for VS Code supports basic authentication and the credentials can be written in the proxy URL, like http://USERNAME:[email protected]:5187/. This is the simplest way. The password is then saved as plain text in your settings file, so never share or commit that file.

Option 2, in a prompt. The VS Code documentation says that behind an authenticated HTTP proxy an authentication popup should appear and that Basic, Digest, NTLM and Negotiate are supported. If you leave the credentials out of the address and the popup appears, type them there.

If the username or password contains special characters, write them percent-encoded in the address: @ becomes %40, : becomes %3A, / becomes %2F, # becomes %23 and % becomes %25. The official pages I read do not describe this; it is the general rule for web addresses, so test it with the check below. Copying the details from My assets is safer than typing them.

• Sources:
• Visual Studio Code docs: Network Connections
• GitHub Docs: Configuring network settings for GitHub Copilot

HTTP or SOCKS5

The VS Code documentation says SOCKS5 proxy authentication is not implemented yet, so for a proxy with a username and password choose HTTP. The Copilot network page does not mention SOCKS.

• Sources:
• Visual Studio Code docs: Network Connections
• GitHub Docs: Configuring network settings for GitHub Copilot

Settings the documents do not describe

VS Code also has a setting named http.proxySupport, but none of the official pages I read describe its values, so this guide does not tell you to change it. If you are curious, search for proxySupport in Settings and read the description shown there. http.proxyAuthorization is named in the VS Code documentation without a description; you do not need it when the credentials are in the address.

• Sources:
• Visual Studio Code docs: Network Connections

Extensions that make their own requests

Many extensions, especially AI coding helpers, connect to their service themselves. The VS Code documentation says extensions do not yet benefit from the same proxy support as the editor, which is why http.proxy matters for them. Whether a particular extension reads http.proxy, has its own proxy field or uses something else is decided by that extension: read its marketplace page and its settings. If one extension still fails after the check below, look for a proxy option in that extension's own settings.

GitHub Copilot uses the same Proxy field described above; the Copilot page has the exact steps and a ready preset. Cursor is built on VS Code and has extra switches of its own, covered in its guide.

• Cursor proxy setup
• GitHub Copilot proxy setup
• GitHub Copilot on Proxy302

• Sources:
• Visual Studio Code docs: Network Connections
• GitHub Docs: Configuring network settings for GitHub Copilot

The terminal inside VS Code

The integrated terminal runs ordinary command-line programs, and each program decides for itself where to find a proxy. The VS Code pages I read say nothing about the terminal, so do not expect http.proxy to apply to what you run there. Most command-line tools read environment variables or their own options. The curl guide lists the variables curl reads and how they interact; for other tools such as git, npm or pip, read their own documentation.

• curl proxy setup

The terminal: example for one session

export https_proxy="http://USERNAME:PASSWORD@HOST:PORT"
export http_proxy="http://USERNAME:PASSWORD@HOST:PORT"
curl https://ipinfo.io/json

Illustrative: these are the names curl reads (see the curl guide); other programs may read other names or none. The variables last only for this terminal window. Replace HOST, PORT, USERNAME and PASSWORD with the values from My assets.

How to check that the proxy works

1. Test the proxy itself in the terminal with the command below

   It shows the IP, country and network that websites see. If this fails, the problem is the proxy details, not VS Code. The guide on how to check your proxy's IP, country and ISP explains the fields.

   • how to check your proxy's IP, country and ISP

2. Quit VS Code completely and start it again

   Close the editor, not only the window, then repeat the action that failed, for example a sign-in or a chat request in an installed add-on.

3. Read the add-on's own error message

   The VS Code documentation does not describe a built-in connection test, so use the add-on's error text and the list below.

Check the proxy outside the editor: example

curl -x http://USERNAME:PASSWORD@HOST:PORT https://ipinfo.io/json

Replace HOST, PORT, USERNAME and PASSWORD with the values from My assets. The answer shows the IP, country and network that websites see.

Common errors

• 407 Proxy Authentication Required. The proxy rejected the username or password. Copy the details again and check the percent-encoding.

• Certificate errors. These happen only with a proxy that rewrites certificates. The VS Code documentation names adding the proxy's certificate to the operating system's trusted certificates as the preferred fix and calls ignoring certificate errors dangerous and not recommended. Do not untick Proxy Strict SSL as a quick fix.

• The editor works but one extension does not. That extension makes its own connection: see the section about extensions.

• Timeouts. The proxy does not answer on the port, or the IP lease has ended. Test with the curl command.

• Sources:
• Visual Studio Code docs: Network Connections

How to do it with Proxy302

A static ISP proxy fits when you want one permanent address for your editor: the IP stays the same for the whole lease and you choose the protocol at purchase. Choose HTTP: the VS Code documentation says SOCKS5 authentication is not implemented yet. The product itself is described on the static residential proxies page.

• static residential proxies

How to do it with Proxy302: steps

1. Step 1

   Open the static ISP page, choose the country, set Protocol to HTTP, choose the term and the quantity, then review the cost and generate.

2. Step 2

   Open My assets and copy HOST, PORT, USERNAME and PASSWORD. The Connect page shows a ready example with your own details. HTTP uses port 2222 on proxy.proxy302.com.

3. Step 3

   Put the values into the Proxy field (http.proxy) as shown above, quit VS Code completely and start it again.

4. Step 4

   Check the exit with the curl command above and read the country and org fields, as the proxy location guide explains.

   • how to check your proxy's IP, country and ISP

Prices and limits

A static ISP IP costs US$0.50 for one day and US$7.99 for 30 days, about US$0.27 per day, the same in every country. Availability by country changes daily and is shown on the order page. There is no free trial, and the smallest purchase is one IP for one day.

• Sources:
• Proxy302 product facts and price list

FAQ

Read next

Cursor proxy setup

Set a proxy in Cursor with http.proxy, handle special characters in the password, switch to HTTP/1.1 when streaming hangs, and verify with Run Diagnostics.

GitHub Copilot proxy setup

Run GitHub Copilot through an HTTP proxy in VS Code and JetBrains IDEs: the proxy field, basic authentication, certificates and a curl check against GitHub's ping address.

Check a proxy's IP, country and ISP

Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.

curl proxy setup

Use an HTTP or SOCKS5 proxy with curl: -x, credentials, socks5h, environment variables, .curlrc and an exit check.

ISP proxies (static residential)

Fixed static ISP proxies: a residential-grade IP that stays the same for the whole term. For social accounts, stores and AI tools. HTTP and SOCKS5.

View options and pricing