Working behind a corporate proxy usually means editing several configuration files by hand: VS Code settings, the Git config, the npm config, the pip config, and the environment variables your terminals inherit. Keeping them aligned, and remembering to turn them all off again, is tedious and error-prone. otak-proxy turns this into a single status bar click. It keeps VS Code, Git, npm, pip, and new integrated terminals in step, and its Auto mode follows your system proxy in the background.

  VS Code status bar (left side)
  ─────────────────────────────────────────────────────────────────
  …  ⟳ Auto: http://proxy.example.com:8080  │  ⚠ 0  ⓘ 0  │  main …
  ─────────────────────────────────────────────────────────────────
     ▲ click to switch between Off and Auto; VS Code, Git, npm,
       pip, and new integrated terminals are updated together

Quick Start

Auto Mode

1. Install from the VS Code Marketplace.
2. On first launch, otak-proxy asks how to configure the proxy. Choose Auto (System) to follow the system proxy. You can also choose Manual Setup to enter a fallback proxy URL and switch to Auto, or Skip and click the status bar later to switch to Auto.
3. otak-proxy applies the system proxy to VS Code, Git, npm, pip, and new integrated terminals.
4. Click the status bar again to switch Off and clear the proxy settings that otak-proxy manages.

Optional Fallback Proxy

1. Run otak: Configure Manual Proxy.
2. Enter a fallback proxy URL (for example, http://proxy.example.com:8080).

Auto mode uses this URL when no system proxy is detected, including when the system proxy disappears while VS Code is running. When you switch to Auto from the status bar and no system proxy is found, or when Auto notices that the system proxy has disappeared, otak-proxy first tests the fallback proxy and uses it only if it is reachable. A URL entered during first-run setup is applied without this test. If the URL includes credentials, read Security & Privacy before allowing otak-proxy to write it to VS Code, Git, npm, or pip configuration files.

When the stored fallback already has credentials, the prompt prefills the URL without them. Submitting it unchanged keeps the stored credentials, entering different credentials replaces them, and entering a different URL without credentials stores none. Setting an invalid value for otakProxy.proxyUrl in settings.json is rejected with an error and is not saved or synced; an invalid value already saved there is ignored wherever the setting is read (it never reaches the fallback or SecretStorage) and is logged once per activation.

Capabilities

• Two-state toggle: switch between Off and Auto from the status bar.
• Auto mode: reads the system proxy and applies changes in the background.
• Optional fallback proxy: uses a configured proxy URL when no system proxy is detected.
• Connection test: otak: Test Proxy checks whether a proxy is reachable.
• Automatic connection testing: in Auto mode, periodically checks that the active proxy is still reachable. Auto turns off (Auto: OFF) only when the proxy cannot be reached at all (the connection is refused or there is no route to it), and turns back on as soon as a test shows that the proxy answers again, even with an error such as 407 or 403, or accepts the connection and then times out (an https: proxy must also finish the TLS handshake). A timeout or DNS failure before the proxy is reached, or a TLS failure, proves neither, so Auto keeps its current state. A newly detected system proxy is tested on its own and starts in Auto unless it cannot be reached.
• Diagnostics and safe remediation: records sanitized diagnostics, retries an eligible failed apply once, and stops repeating repairs when another tool keeps rewriting the settings.
• Ownership-aware cleanup: Off removes only the values otak-proxy wrote; values set or changed by you or other tools are kept.
• Credential-aware storage: stores proxy credentials in VS Code SecretStorage where available and keeps synced and global state free of credentials.
• Windows diagnostics: reads WinINET, WinHTTP, PAC, and WPAD state without changing Windows settings. WinHTTP reset is available only as a command you run and confirm.
• Multi-instance sync: shares proxy settings across all open VS Code/Cursor windows.
• Integrated terminals: sets HTTP_PROXY and HTTPS_PROXY for new VS Code terminals.
• URL visibility: hide the proxy URL in the status bar when needed.
• Localized interface: the UI follows your VS Code display language, in 16 languages.

How It Works

Status Bar

Click the proxy indicator to switch between the two states:

         click              click
  ┌─────┐ ────▶ ┌──────┐ ────▶ ┌─────┐
  │ Off │        │ Auto │        │ Off │  …
  └─────┘        └──────┘        └─────┘

There is no separate Manual mode. A URL entered with otak: Configure Manual Proxy is stored as the Auto fallback and is used when no system proxy is detected. Manual mode states saved by older versions are migrated to Auto when they are loaded.

Status Indicators

  ┌──────────────────────────────────────────┐
  │ ⊘ Proxy: Off                             │  proxy disabled; managed settings cleared
  ├──────────────────────────────────────────┤
  │ ⚠ Proxy: Off                             │  switched off, but a value was kept because
  │                                          │  otak-proxy could not verify that it wrote
  │                                          │  it (see Troubleshooting)
  ├──────────────────────────────────────────┤
  │ ⟳ Auto: http://proxy.example.com:8080    │  following the detected system proxy
  ├──────────────────────────────────────────┤
  │ ⌁ Auto (Fallback): http://192.168.1.2:88 │  no system proxy; using your configured
  │                                          │  fallback URL (plug icon)
  ├──────────────────────────────────────────┤
  │ ⚠ Auto: PAC unsupported                  │  PAC / GNOME auto / similar auto-config
  │                                          │  was detected; otak-proxy cannot resolve it
  ├──────────────────────────────────────────┤
  │ ⌁ Auto (Fallback, ignoring PAC): url     │  unsupported auto-config; using your
  │                                          │  configured fallback and saying so
  ├──────────────────────────────────────────┤
  │ ⊘ Auto: OFF                              │  no reachable proxy right now; retested
  │                                          │  automatically in the background
  ├──────────────────────────────────────────┤
  │ ⚠ Auto: http://proxy.example.com:8080    │  last apply failed on some target —
  │                                          │  hover for details
  ├──────────────────────────────────────────┤
  │ ⚠ Auto (blocked)                         │  apply was refused (for example an
  │                                          │  untrusted workspace, or proxy credentials
  │                                          │  still waiting for your consent); desired
  │                                          │  Auto is not treated as applied
  └──────────────────────────────────────────┘

The glyphs above stand for the VS Code codicons $(circle-slash) (⊘), $(sync) (⟳), $(plug) (⌁), and $(warning) (⚠). When the last apply failed or was blocked, ⚠ replaces the usual icon of the current state. In Off, ⚠ means the last switch-off kept a value it could not verify as its own.

When otakProxy.showProxyUrl is false, the URL is replaced with Configured (for example, Auto: Configured). Set it back to true, or use the Show URL link in the tooltip, to display the address.

The detailed hover tooltip is enabled by default. The otak-proxy status bar items sit on the left side so their tooltips do not cover VS Code notifications on the right. Set otakProxy.statusBarTooltip to false to hide the tooltip.

Auto Detection Scope

Auto detection tries the sources in otakProxy.detectionSourcePriority: environment variables, VS Code settings, and platform proxy settings. Behavior can differ between local Windows, macOS, Linux, WSL, containers, and remote extension hosts. Windows registry and WinHTTP actions are available only when the extension host runs on local Windows.

PAC, WPAD, and GNOME mode=auto are reported as detected but unsupported (kind: pac|wpad, capability unsupported), not as "no proxy". otak-proxy does not include a PAC/WPAD engine. When the fallback URL is used instead, the status bar says that the auto-config is being ignored.

A platform query that fails (a registry query error or timeout, gsettings or networksetup failing, a GNOME manual-mode host/port that cannot be read) is reported as unknown, not as "no proxy". In Auto mode the last known proxy stays applied to Git, npm, VS Code, and the terminal, no fallback is engaged, and no "system proxy removed" notice is shown; the background check retries with backoff (otakProxy.maxRetries) and warns once all retries failed. otak: Import System Proxy says that detection failed instead of "no system proxy", toggling from Off to Auto keeps Off, writes nothing, and shows "System proxy detection failed" instead of engaging the fallback or asking to configure a proxy, and the first-run Auto setup offers Configure Manual or Redetect; if neither is chosen, or the URL prompt of Configure Manual is cancelled, the setup is offered again on the next start. Not having the setting at all is still "no proxy": a Windows user without the Internet Settings registry key (recognized from the English reg message only; on a non-English Windows the missing key stays unknown), Linux without gsettings, without the GNOME proxy schema, or with no compiled schemas at all (No schemas installed; non-GNOME desktops, CI) is not an error. gsettings is run with LANGUAGE=C and LC_MESSAGES=C so that the missing-schema message is recognized on a non-English desktop. When the platform query fails but a later source in otakProxy.detectionSourcePriority finds a proxy, that proxy is used.

Windows: ProxyEnable=0 with AutoConfigURL is reported as unsupported PAC. A registry AutoDetect=1 bit without AutoConfigURL is reported as unsupported WPAD as a registry observation only; whether WPAD was the effective path has not been confirmed on a test machine.

macOS: network services are listed with networksetup -listallnetworkservices, skipping disabled services (marked *). A usable web or secure web proxy on any listed service is used; an enabled auto-proxy URL is reported as unsupported PAC. If the list succeeds but every service is disabled, there is no proxy. If listing fails, the three well-known services Wi-Fi, Ethernet, and Thunderbolt Ethernet are checked instead. If a query on a listed service fails and no service has a manual proxy, the result is unknown, even when another service answered "no proxy" or has a PAC URL; when the listing itself failed and the well-known names are used, unknown is reported only if every query fails (a name that does not exist on the Mac is expected to fail). Which service is the effective default route has not been verified on a macOS test machine.

Windows ProxyServer may be one endpoint (host:8080, a trailing ; is accepted) or scheme=endpoint parts separated by ; or spaces (http=a:80 https=b:80). ProxyEnable and AutoDetect are on when the REG_DWORD value is a non-zero number (0x1, 0x11, 1), in detection and in diagnostics alike.

Integrated Terminal Environment

When the proxy is enabled, otak-proxy sets these variables for newly created VS Code integrated terminals:

• HTTP_PROXY / HTTPS_PROXY
• http_proxy / https_proxy on non-Windows hosts

Existing terminals keep their current environment; open a new terminal to pick up the updated values.

When proxy mode is Off and otakProxy.terminalOffMaskingEnabled is enabled, otak-proxy masks HTTP_PROXY / HTTPS_PROXY (and the lowercase variants on non-Windows hosts) in new terminals by setting them to empty values. This stops tools launched from VS Code from using a proxy inherited from the editor process. NO_PROXY / no_proxy / ALL_PROXY / all_proxy are left unchanged unless otak-proxy wrote them earlier.

Windows Environment Variable Check

On local Windows, otak-proxy compares the saved user and system values of HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY with the environment of the running VS Code process. When they differ, it shows a warning that lists only the variable names. Values and credentials are never shown.

• If a variable is saved for both the user and the system, the user value is compared.
• The check runs at startup and about every 60 seconds while the VS Code window is focused. The same mismatch is reported only once, and at most one warning is shown every 5 minutes. If the saved values cannot be read, the check waits longer between attempts (up to about 15 minutes).
• A variable is compared only after a saved value has been seen for it. A value that exists only in the VS Code process from startup cannot be told apart from an intentional temporary setting, so it is not reported. Removing a saved value after it has been seen is reported.
• The saved values are read with two reg query calls on the user and system Environment registry keys; no PowerShell is started. A saved value that contains non-ASCII characters is not compared, because reg query prints it in the console code page.
• The check is read-only. It does not change environment variables and does not affect Auto detection or proxy application.
• Set otakProxy.notificationLevel to "off" to turn the warning off. The check then does not run at all, so no process is started.

If you see the warning, save your work, quit every VS Code window, start VS Code again, and open new terminals. Reloading the window may not refresh the environment. If the launcher or shell that starts VS Code still has the old environment, you may also need to restart it or sign out and back in.

Settings

Common Settings

{
  "otakProxy.proxyUrl": "http://proxy.example.com:8080",
  "otakProxy.pollingInterval": 30,
  "otakProxy.enableFallback": true,
  "otakProxy.showProxyUrl": true,
  "otakProxy.statusBarTooltip": true,
  "otakProxy.autoTestEnabled": true,
  "otakProxy.testInterval": 60,
  "otakProxy.credentialTargetPolicy": "ask"
}

For stricter corporate environments, use:

{
  "otakProxy.credentialTargetPolicy": "blockPlaintextTargets"
}

Advanced Settings

{
  "otakProxy.syncEnabled": true,
  "otakProxy.syncInterval": 1000,
  "otakProxy.detectionSourcePriority": ["environment", "vscode", "platform"],
  "otakProxy.ignoreSelfWrittenVSCodeProxy": true,
  "otakProxy.maxRetries": 3,
  "otakProxy.diagnosticsEnabled": true,
  "otakProxy.automaticRemediationEnabled": true,
  "otakProxy.hostUserLockEnabled": true,
  "otakProxy.automaticRetryEnabled": true,
  "otakProxy.remediationDelayedRetryMs": 2000,
  "otakProxy.remediationFlapWindowMs": 600000,
  "otakProxy.remediationFlapMaxAttempts": 2,
  "otakProxy.remediationFlapCooldownMs": 600000,
  "otakProxy.notificationCooldownMs": 600000,
  "otakProxy.slowDiagnosticsTtlMs": 300000,
  "otakProxy.terminalOffMaskingEnabled": true,
  "otakProxy.notificationLevel": "warnings",
  "otakProxy.windowsActionsEnabled": false
}

Commands

Open the Command Palette (Cmd/Ctrl+Shift+P) and run:

• otak: Toggle Proxy
• otak: Test Proxy
• otak: Import System Proxy
• otak: Configure Manual Proxy
• otak: Toggle Proxy URL Visibility
• otak: Diagnose Proxy State
• otak: Reset WinHTTP Proxy

Security & Privacy

Local Configuration Changes

• VS Code: writes the global http.proxy setting through the VS Code configuration API. In a remote window (SSH, WSL, dev container, Codespaces) otak-proxy neither writes nor removes it; see Troubleshooting.
• Git: writes the global http.proxy with git config --global. Git uses this single key for both HTTP and HTTPS remotes (HTTPS goes through CONNECT). https.proxy does not route traffic, so otak-proxy does not write it; Off still removes a leftover https.proxy that otak-proxy owns.
• npm: writes the user-level proxy and https-proxy with npm config set. Off looks at the npm user config file (.npmrc) only, the layer npm config set and npm config delete act on, and removes a value from it only when it is the one otak-proxy wrote. This is also how it reads a proxy URL with a password, which npm config get refuses to print (npm 10.8 and later). A value npm loads from a project or global .npmrc or from the environment (npm_config_proxy and the like), or a value in a form otak-proxy never writes, is not otak-proxy's: Off never removes it, and the npm target is reported as an external override (advisory) instead of a failure. A missing user config file counts as an empty layer. If npm will not say where its user config file is, Off falls back to the value npm config get reports.
• pip: writes the user-level global.proxy with python -m pip config --user (trying py, python, then python3 on Windows, and python3, then python elsewhere). pip stores one URL for both HTTP and HTTPS. This target is skipped when Python or pip is not installed.
• Integrated terminals: sets HTTP_PROXY and HTTPS_PROXY for new terminals, plus the lowercase variants on non-Windows hosts.
• Off removes only the values that otak-proxy wrote and that have not changed since. Values that you or other tools set or changed are kept.
• Deactivating or uninstalling the extension does not clean up these settings by itself. Switch Off before uninstalling, or follow Troubleshooting.

Credentials

• No account or API key is required.

• Use a proxy URL with credentials only when your proxy requires them. otak-proxy stores the credential part in VS Code SecretStorage where available and keeps global state and sync data free of credentials.

• VS Code, Git, npm, and pip read their own configuration files, so applying a proxy URL with credentials writes those credentials in plaintext to files such as settings.json, .gitconfig, .npmrc, and the pip user config file.

• otakProxy.credentialTargetPolicy controls this:

  • ask (default): asks once per proxy address on each machine before writing its credentials; a remote host counts as its own machine. One prompt covers every credential-bearing URL an apply writes, including the HTTPS URL of a per-scheme proxy. The apply that needs your answer stops at once and the status bar shows Auto (blocked); the prompt is shown on its own and nothing waits for it, so other toggles and applies are not held up. Allow Plaintext Write records your consent and applies the current proxy once. Deny or closing the prompt records nothing and the status bar stays Auto (blocked) until the next apply or toggle. Switching Off while the prompt is open clears the blocked state, and answering Allow afterwards applies nothing. Reloading the window drops an open prompt; the blocked state stays until the next apply. Background applies are skipped without a prompt until you allow it.
  • allowPlaintextTargets: writes without asking.
  • blockPlaintextTargets: never applies a proxy URL with credentials. Use it when your organization forbids credentials in tool config files.

• VS Code Settings Sync copies the http.proxy value in settings.json, credentials included, to your other machines. If you apply a proxy URL with credentials, add http.proxy to the ignored settings first, so the credentials do not leave this machine:

  "settingsSync.ignoredSettings": ["http.proxy"]
  

• If a proxy URL's credentials cannot be restored on this machine — for example storing them in SecretStorage failed — otak-proxy skips the apply instead of writing the URL without its credentials. This covers every apply: the system-proxy monitor, the toggle, sync, and startup, not only the startup check. For a per-scheme proxy this applies per address: the apply is skipped when any address that needed credentials cannot restore them.

• Passwords, authorization headers, npm tokens, Git extra headers, command output, copied diagnostics, control characters, and sync data are redacted before they are logged or displayed.

Network Activity

• otak-proxy sends no telemetry and does not transmit usage data.
• Connection tests check reachability by sending HTTP CONNECT requests through the configured proxy to the default test hosts www.github.com, www.microsoft.com, and www.google.com. The test opens its own TCP (or TLS) connection to the proxy under test, so it never goes through the proxy in http.proxy or VS Code's http.proxySupport handling. For an https:// proxy, the test checks the proxy's certificate against Node's built-in CA list and NODE_EXTRA_CA_CERTS. It also trusts the operating system's certificate store only when VS Code's http.experimental.systemCertificatesV2 is on (with http.systemCertificates on, the default).
• If the proxy URL contains credentials, the test sends a Proxy-Authorization header to the configured proxy. Test results, logs, and diagnostics redact credentials and authorization headers.
• For diagnostics and Auto detection, the extension reads local environment variables, VS Code settings, the Git config, the npm config (including the npm user config file when npm will not print a proxy URL with a password), and supported platform proxy settings.

Diagnostics and Remediation Behavior

Run otak: Diagnose Proxy State to inspect the current proxy state. Diagnostics are read-only: they collect sanitized observations from VS Code, the terminal environment, the Git config, the npm config, the execution context, and supported Windows proxy sources. The command always reads fresh values. Diagnostics also run automatically after each proxy apply. They read fresh values after a successful apply, after a retry, and when the apply was skipped because another window holds the apply lock. They reuse cached results of slow command-based checks (up to otakProxy.slowDiagnosticsTtlMs old) in two cases: when an apply failed and is not retried, and when the credential policy stopped the apply. This keeps Git, npm, and Windows commands from launching again right after the failure.

Diagnostics also check whether the actual tool settings match the selected state:

• In Auto with an active proxy, diagnostics report a mismatch when VS Code, Git http.proxy, or npm no longer holds the expected proxy URL. This check covers only the targets that otak-proxy has recorded as configured. A leftover Git https.proxy is reported for information only, because Git does not route traffic through it.
• In Off, or in Auto while it shows Auto: OFF, diagnostics report a residual when VS Code, Git, or npm still has a proxy configured. A value that otak-proxy left in place when it cleared proxy settings, because otak-proxy did not write it, is reported as an advisory, not as a failure. An unsupported auto-config setting (PAC, WPAD, or GNOME mode=auto) is reported for information only in these states, because otak-proxy neither uses nor changes it.
• When Git or npm cannot be read (for example, the command is not on PATH or times out), diagnostics report that for information and skip the mismatch and residual checks for that tool, instead of treating it as having no proxy.
• In remote, WSL, container, or web extension hosts, local Windows checks that cannot run there are reported as capability limits instead of being forced.

When otak-proxy starts in Off or Auto: OFF, it runs the same disable path as switching Off, so leftover VS Code, Git, or npm proxy entries that otak-proxy manages are detected and cleared.

When otakProxy.automaticRemediationEnabled is enabled, remediation after an apply is limited and safe:

• An eligible apply failure, residual, or mismatch is retried once after otakProxy.remediationDelayedRetryMs, followed by fresh diagnostics.
• If repairs keep failing for the same issue, further attempts are suppressed for the flap window and cooldown.
• Locks shared by all windows prevent two windows from writing at the same time.
• Disruptive Windows actions, such as WinHTTP reset, still require you to run the command and enable otakProxy.windowsActionsEnabled.

The diagnostics report keeps the recorded result and the fresh observation apart:

• recordedRuntimeState is what the last apply recorded. runtimeState also counts convergence-blocking issues found in this run, so a recorded success with a fresh residual is reported as partial, not applied.
• desired is the selected mode, and converged says whether the tool settings actually match it. Selecting Off does not by itself mean the settings were cleared. converged is true only when runtimeState is applied, so a failed or blocked apply is never reported as converged.
• lastRemediation is the outcome of the most recent proxy apply in this VS Code window: per-target results, whether the retry ran, the stop reason (converged, unverified, retryExhausted, retryDisabled, notRetryable, flapSuppressed, lockSkipped, lockIoError, superseded, or consentRequired), and the IDs of the remaining blockers. It never contains proxy URLs, credentials, or command output, and it is null until the first apply in the window finishes.

Language Support

The interface follows your VS Code display language. 16 languages are available, covering the main languages of every G20 country:

English · Japanese (日本語) · Simplified Chinese (简体中文) · Traditional Chinese (繁體中文) · Korean (한국어) · Vietnamese (Tiếng Việt) · Spanish (Español) · Brazilian Portuguese (Português) · French (Français) · German (Deutsch) · Hindi (हिन्दी) · Indonesian (Bahasa Indonesia) · Italian (Italiano) · Russian (Русский) · Arabic (العربية) · Turkish (Türkçe)

Requirements

• VS Code 1.97.0 or newer
• Cursor, when it supports the required VS Code extension API version
• Git on PATH (git --version)
• Optional: Python with pip, if you want otak-proxy to manage the pip proxy

Installation

Install from the VS Code Marketplace, or run this in the Quick Open box (Cmd/Ctrl+P):

ext install odangoo.otak-proxy

npm ci
npm run package:vsix
code --install-extension otak-proxy-<version>.vsix

Troubleshooting

• The proxy does not work: make sure the URL starts with http:// or https://, then run otak: Test Proxy.

• "System proxy detection failed after multiple retries. Check your system/browser proxy settings." (also the wording of the otak: Import System Proxy warning "System proxy detection failed"): the operating system's proxy settings could not be read, which is different from "no system proxy". The proxy that was applied before stays in place and Git, npm, VS Code, and the terminal are not changed. The warning is shown as a 10 second status bar message (UserNotifier.showWarning, src/errors/UserNotifier.ts:93-96, triggered from src/core/ExtensionInitializer.ts:122-128), and it repeats after each failed round of retries for as long as the query keeps failing. Check the tool for your platform: Windows reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings", macOS networksetup -listallnetworkservices and networksetup -getwebproxy Wi-Fi, Linux gsettings list-recursively org.gnome.system.proxy. Run otak: Diagnose Proxy State; if it keeps happening, set the proxy with otak: Configure Manual Proxy.

• Settings look correct, but tools still use the old proxy: run otak: Diagnose Proxy State. Existing terminals and some VS Code process-level proxy settings need a new terminal, a window reload, or a full VS Code restart.

• "Failed to toggle proxy mode": the saved proxy state kept changing while the toggle was saving it — for example another VS Code window or the background check saved at the same time — so the toggle changed nothing. Click the status bar again. If it keeps failing, reload the window and check the otak-proxy output log.

• "The initial proxy setup could not be saved...": the saved proxy state kept changing while your first-run answer was being saved, so the answer was not stored. The setup prompt is offered again the next time the window starts; answer it then. If it keeps failing, check the otak-proxy output log.

• A warning says saved Windows proxy environment settings differ from this VS Code process: quit every VS Code window, start VS Code again, and open new terminals (see Windows Environment Variable Check).

• "Proxy turned off, but some values were kept because otak-proxy could not verify that it wrote them: ..." (the status bar shows ⚠ Proxy: Off): the named setting holds a proxy URL with credentials, and the record that proves otak-proxy wrote it, or the key that checks the password, is missing on this machine (for example after clearing VS Code's stored secrets). Off keeps such a value instead of guessing. Either turn the proxy on again and then off, which writes a fresh record and lets Off remove the value, or delete the listed value by hand as shown in the next entry. A value you set yourself is not part of this warning: Off keeps it silently.

• Proxy settings remain after switching Off or uninstalling: switch otak-proxy Off first, then run otak: Diagnose Proxy State. If settings still remain, check them and remove only the entries you no longer want:

  git config --global --get http.proxy
  git config --global --get https.proxy
  git config --global --unset http.proxy
  git config --global --unset https.proxy
  npm config list
  npm config delete proxy
  npm config delete https-proxy
  python -m pip config --user get global.proxy
  python -m pip config --user unset global.proxy
  

  npm config list shows proxy and https-proxy with any password masked; npm refuses npm config get for a proxy URL that contains one. On Windows, use py -m pip if python is not on PATH. Also check http.proxy in your VS Code User Settings and clear it if it should no longer be set.

• Git is not detected: make sure Git is installed and on PATH (git --version).

• Auto mode does not pick up changes: check your system proxy settings and adjust otakProxy.pollingInterval.

• Remote, WSL, or container windows: Windows registry and WinHTTP actions are available only when the extension host runs on local Windows. Remote hosts are diagnosed as remote targets, and Windows actions are skipped.

• In a remote window (SSH, WSL, dev container, Codespaces), Diagnose says otak-proxy does not write or remove VS Code's http.proxy: VS Code decides whether a write from a remote window goes to the local or the remote settings (it depends on http.useLocalProxyConfiguration), and otak-proxy cannot tell where it would land, so it writes and removes nothing there. Git, npm, pip, and terminal variables on the remote host are handled as usual. To route VS Code itself through the proxy, run Preferences: Open Remote Settings and set http.proxy there, or turn on http.useLocalProxyConfiguration. A value that an older version wrote to http.proxy from a remote window is no longer removed: remove it by hand from the settings file that holds it. After the update, Off in a remote window removes only values that otak-proxy applied there after the update; remove older values by hand, or apply once before turning the proxy off.

• Linux/BSD: proxy settings do not apply and lastRemediation.stopReason is lockIoError: otak-proxy cannot use its lock directory, <temp>/otak-proxy-<uid>, where <temp> is $TMPDIR or /tmp. The directory must be a real directory that your user owns, with no group/other permissions. Correct its owner and mode, or remove it. If another account owns it, set TMPDIR to a private directory before starting VS Code, or ask an administrator to remove it. Git writes report a permission error in the same case.

Related Extensions

More VS Code extensions by odangoo:

License

Released under the MIT License.