You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows behind a corporate HTTP proxy, web_fetch and auto-update fail with TypeError: fetch failed, even when HTTP_PROXY and HTTPS_PROXY are set as documented in copilot help environment. curl.exe through the same proxy works fine, so the proxy itself
is not the issue.
My best guess for the root cause: copilot.exe appears to be a self-contained executable
that may ship with an embedded Node.js runtime. If that runtime is older than v23.8.0, native fetch (undici) would silently ignore proxy env vars, since NODE_USE_ENV_PROXY=1 support
was only added in v23.8.0. Switching the system Node via nvm has no effect, which is
consistent with this theory — but I'm not certain this is the actual cause.
Affected version
GitHub Copilot CLI 1.0.3 (Installed via MSI from GitHub Releases)
Describe the bug
On Windows behind a corporate HTTP proxy,
web_fetchand auto-update fail withTypeError: fetch failed, even whenHTTP_PROXYandHTTPS_PROXYare set as documented incopilot help environment.curl.exethrough the same proxy works fine, so the proxy itselfis not the issue.
My best guess for the root cause:
copilot.exeappears to be a self-contained executablethat may ship with an embedded Node.js runtime. If that runtime is older than v23.8.0, native
fetch(undici) would silently ignore proxy env vars, sinceNODE_USE_ENV_PROXY=1supportwas only added in v23.8.0. Switching the system Node via
nvmhas no effect, which isconsistent with this theory — but I'm not certain this is the actual cause.
Affected version
GitHub Copilot CLI 1.0.3 (Installed via MSI from GitHub Releases)
Steps to reproduce the behavior
copilot—Error auto updating: TypeError: fetch failedappears on startupweb_fetch— sameTypeError: fetch failedExpected behavior
HTTP_PROXY/HTTPS_PROXYshould be respected for all outgoing connections, as documented incopilot help environment.Additional context
nvm use 23.8.0+ restartingcopilothas no effect (suggesting the bundled runtime is used regardless of system Node)copilot.execonnections through the proxy at OS level