No automatic proxy forwarding to launched Edge instance in corporate environments

Environment

• OS: Windows 10/11 (corporate domain-joined)
• Extension version: latest
• VS Code: 1.90+
• Deployment: Behind corporate HTTPS proxy (NTLM/Kerberos or basic auth), proxy configured via system settings or HTTPS_PROXY env var

Description

When the extension launches an Edge instance via puppeteer (in launchBrowser in src/utils.ts), it does not automatically forward the OS-level proxy configuration to the launched browser. The browser is spawned without --proxy-server in its args unless the user manually adds it via the vscode-edge-devtools.browserArgs setting.

In corporate environments where all outbound traffic routes through a proxy, the embedded Edge instance cannot reach remote targets, and developers see connection failures with no actionable guidance.

The same issue applies to the --proxy-bypass-list flag — there is no way to exempt localhost from the proxy automatically.

Steps to Reproduce

1. Configure a corporate proxy via Windows system proxy settings (or HTTPS_PROXY/HTTP_PROXY env vars).
2. Open a project in VS Code and launch the Edge DevTools extension browser preview.
3. The launched Edge instance bypasses the system proxy and connection fails.

Expected Behavior

The extension should either:

1. Detect and forward the OS/VS Code proxy settings (http.proxy, HTTPS_PROXY) to the Edge launch args automatically as --proxy-server=<value> and --proxy-bypass-list=localhost, OR
2. Document clearly in README/settings description that users must manually add --proxy-server=http://corp-proxy:8080 via vscode-edge-devtools.browserArgs to use the extension behind a corporate proxy.

Actual Behavior

No proxy is forwarded. The browserArgs setting description does not mention proxy usage. Users in corporate environments discover this only after connection failures, with no guidance in logs or docs.

References

• src/utils.ts:398-422 — launchBrowser builds args from getBrowserArgs() only; no proxy derivation from env or VS Code settings
• VS Code's own http.proxy setting is not consulted here

Start in src/utils.ts:398-422, especially launchBrowser and getBrowserArgs, and review the browserArgs setting description. Decide whether the intended resolution is proxy forwarding or documentation, then verify that corporate proxy users receive working guidance or that the launched Edge instance receives the relevant proxy and bypass settings.