Skip to content

Cline, Roo Code and Aider Proxy Setup: One Pattern

Where each AI coding tool reads its proxy, and a test that shows whether it is used.

Where each tool takes its proxy from

Where each tool takes its proxy from
ItemWhere the proxy is setProtocol limitsAfter you change it
Cline in VS CodeVS Code's own proxy settings (http.proxy); Cline needs nothing extraHTTP proxy; an authenticated one shows a login popup; SOCKS5 authentication is not implemented in VS CodeRestart so Cline picks it up
Cline CLIEnvironment variables https_proxy, http_proxy, no_proxyHTTP proxies only; no SOCKS, no PACSet them before you run cline; restart after changes
Roo CodeNo proxy documentation found; its repository is archived and the extension was shut down on 15 May 2026Not applicableIf you use a fork, follow the fork's own documentation
AiderEnvironment variables HTTP_PROXY, HTTPS_PROXY, NO_PROXY, which LiteLLM reads; Aider's docs have no proxy pageUse an HTTP proxy address; test the exit before you rely on itSet the variables in the shell before you start aider

From the Cline, VS Code, LiteLLM and Aider documentation and the Roo Code repository, read on 19 November 2026. Confirm on the live pages: these tools change often.

Cline in VS Code: set the proxy in VS Code

The Cline docs say the VS Code extension automatically uses VS Code's built-in proxy settings, so you do not configure anything inside Cline. Set the proxy in VS Code (the http.proxy setting, or the system proxy that VS Code reads), then restart VS Code: Cline does not notice proxy changes while it runs.

A proxy that needs a username and password makes VS Code show an authentication popup (Basic, Digest, NTLM and Negotiate are supported). SOCKS5 authentication is not implemented in VS Code, so a SOCKS5 proxy with a login is the wrong choice here; take the HTTP one.

Roo Code ran inside VS Code too, but its repository was archived on 15 May 2026 and the extension shut down, and no proxy documentation for it was found. If you use a fork of it, check that fork's own documentation; the VS Code setting above is where VS Code-based extensions generally read the proxy.

Cline CLI and Aider on macOS or Linux

export https_proxy="http://LOGIN:PASSWORD@HOST:PORT"
export http_proxy="$https_proxy"
export no_proxy="localhost,127.0.0.1"
# Aider reads the upper-case names through LiteLLM
export HTTPS_PROXY="$https_proxy"
export HTTP_PROXY="$https_proxy"
export NO_PROXY="$no_proxy"

cline    # or: aider

Example, not a tested script: replace LOGIN, PASSWORD, HOST and PORT with the values of an HTTP IP from My assets. Credentials sit in the URL, as the Cline docs show; they can end up in shell history, so prefer a profile file you control.

Cline CLI on Windows PowerShell

$env:https_proxy = "http://LOGIN:PASSWORD@HOST:PORT"
$env:http_proxy = $env:https_proxy
$env:no_proxy = "localhost,127.0.0.1"

cline

Example: the variables last for this PowerShell window. Set them as user environment variables if you want them permanent, then open a new window.

Aider: set the variables, then test

Aider connects to model providers through LiteLLM, and LiteLLM's documentation says it reads HTTP_PROXY, HTTPS_PROXY and NO_PROXY from the environment for every model request, with no extra flag, as long as they are set before the program starts. Aider's own documentation does not describe proxy handling, so treat that as the expected behaviour and confirm it yourself with the test below.

Export the variables in the shell, start aider from that same shell, and keep NO_PROXY for localhost so a local model server is not sent through the proxy. A different shell window does not inherit them.

Check that the tool really goes through the proxy

  1. Step 1: Test the proxy without the tool

    Run curl through the proxy and read the ip and country fields. If this fails, no AI tool will work either; fix it first.

  2. Step 2: Set the proxy where the tool reads it

    VS Code setting for Cline in VS Code, environment variables for Cline CLI and Aider, as in the table.

  3. Step 3: Restart and run a small task

    Restart VS Code or start the CLI from the shell that has the variables, then ask the tool for something that needs a model reply.

  4. Step 4: Read the log when it fails

    For Cline CLI, cline doctor log opens the log; look for connection, proxy authentication or certificate lines.

Test command

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

Example for an HTTP IP. The country field must be the one you ordered. Use socks5h:// in place of http:// only for tools that support SOCKS5, which Cline CLI does not.

When the proxy does not work in the tool

Connection error with a SOCKS5 address

Check Cline CLI supports only HTTP proxies, and VS Code has no SOCKS5 authentication.

Fix Use the HTTP address and port 2222, or buy the IP as HTTP.

The proxy asks for a login or answers 407

Check Are LOGIN and PASSWORD copied exactly, with no spaces or missing characters? Is the IP still active?

Fix Copy them again from My assets; in VS Code enter them in the authentication popup.

Certificate errors

Check Is a custom CA certificate involved on your network?

Fix Add the certificate to the OS trust store (VS Code) or set NODE_EXTRA_CA_CERTS (Cline CLI). The docs call turning off certificate checks not recommended.

curl works but the tool still goes direct

Check Were the variables set in the same shell that started the tool, and was the tool restarted after the change?

Fix Set them again in that shell and restart the tool. For Aider, check that DISABLE_AIOHTTP_TRUST_ENV is not set.

Stop when If curl works and the tool still does not use the proxy after a restart, that tool does not read the variable; use a setting it documents instead.

With a Proxy302 IP: steps

  1. Step 1: Order an HTTP IP

    Open the static ISP page, choose the country, lease term and HTTP. If the tool uses a Claude, ChatGPT or Gemini account, use the AI-subscription ISP tier that matches it and keep the IP the same as for that account.

  2. Step 2: Copy the details

    In My assets copy HOST, PORT, USERNAME and PASSWORD. HTTP uses port 2222 on proxy.proxy302.com.

  3. Step 3: Put them where the tool reads them

    Use the VS Code setting or the environment variables above, with the address written as http://LOGIN:PASSWORD@HOST:PORT.

  4. Step 4: Run the test command and the tool

    Run the curl test, then restart the tool and give it a small task.

Prices and limits

A static ISP IP is US$0.50 for one day, US$1.50 for 3 days, US$3.50 for 7 days and US$7.99 for 30 days, the same in every country (about US$0.27 a day on the 30-day term, 7.99 ÷ 30). Stock changes daily, so the order page shows what is available. Auto-renew is optional and set per IP in My assets. There is no free trial; the smallest purchase is one IP for one day.

A proxy changes the address the provider sees. It does not change provider rules, raise limits or unban an account.

Cline, Roo Code and Aider proxy FAQ

Does Cline have its own proxy setting?

Not in VS Code: the extension uses VS Code's proxy settings. Cline CLI uses the https_proxy, http_proxy and no_proxy environment variables.

Can Cline use a SOCKS5 proxy?

Cline CLI supports only HTTP proxies, and VS Code has not implemented SOCKS5 authentication. Use an HTTP address.

Is Roo Code still available?

Its GitHub repository was archived by the owner on 15 May 2026 and the README says the extension was shut down. No proxy documentation for it was found.

How do I make aider use a proxy?

Export HTTPS_PROXY, HTTP_PROXY and NO_PROXY in the shell before starting aider; LiteLLM, which aider uses, reads them. Aider's docs have no proxy page, so test the exit with curl and a small task.

Do I need a residential IP for these tools?

The tools only need a working HTTP proxy. The type of IP matters when an account at the model provider is tied to a country or an address; then keep one fixed IP in a supported country for that account.

Further reading

Setup guides Proxy302 publishes on GitHub on the same topic:

Reference links

6
  1. Cline docs: Networking and proxies

    Official documentation · Confirmed on:

    Read on 19 November 2026: the VS Code extension uses VS Code's built-in proxy settings and needs nothing extra; the Cline CLI uses https_proxy, http_proxy and no_proxy (plus NODE_EXTRA_CA_CERTS for a custom certificate) with credentials written in the proxy URL; "Cline CLI only supports HTTP proxies", with no SOCKS or PAC; Cline does not pick up proxy changes while running, so restart after changing them; the log is opened with cline doctor log.

  2. Visual Studio Code docs: Network connections

    Official documentation · Confirmed on:

    Read on 19 November 2026: VS Code has the same proxy support as Chromium and picks up system proxy settings; the settings http.proxy, http.proxyStrictSSL and http.proxyAuthorization; authenticated proxies (Basic, Digest, NTLM, Negotiate) show an authentication popup; SOCKS5 authentication is not implemented; the preferred fix for certificate errors is adding the proxy's certificate to the OS trust store.

  3. Roo Code repository on GitHub

    Third-party source · Confirmed on:

    Read on 19 November 2026: the repository is marked as a public archive, archived by its owner on 15 May 2026 and read-only; the README says the Roo Code extension was shut down on 15 May. The page has no proxy documentation.

  4. Aider docs: Connecting to LLMs (other providers)

    Official documentation · Confirmed on:

    Read on 19 November 2026: "Aider uses the LiteLLM package to connect to LLM providers". The page does not mention proxy variables.

  5. LiteLLM docs: Security settings

    Official documentation · Confirmed on:

    Read on 19 November 2026: LiteLLM resolves HTTP_PROXY, HTTPS_PROXY and NO_PROXY from the environment for every LLM request, on both its default aiohttp transport and the httpx transport; no extra flag is needed, set the variables before the program starts; DISABLE_AIOHTTP_TRUST_ENV=True makes the aiohttp transport ignore them.

    This is LiteLLM's own documentation. Aider's docs do not describe proxy handling, so test the exit as shown instead of assuming it.

  6. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site, checked 19 November 2026: prices in US$ (1 PTC = US$1), protocols and ports (HTTP 2222, SOCKS5 3333), lease terms, no free trial, optional auto-renew.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.