v1.17.2

This release fixes two proxy bugs: a reload prompt that came back on every launch in Remote-SSH windows, and API requests that kept using a removed http.proxy. It also logs the full session ID, so one search finds a session across every Coder log.

Bug fixes

• No more reload prompt on every launch. Remote-SSH starts the server with http.useLocalProxyConfiguration off, so once the remote connects, VS Code reads the http.* proxy settings from the remote. The extension took that switch for a user change and asked "HTTP Proxy, HTTP Proxy Support settings changed. Reload window to apply." each time. It now keeps the local values, so API requests and the SSH connection share one proxy. (#1160, fixes #1161)
• Removing http.proxy takes effect immediately. The extension hands the proxy to coder ssh through HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. With http.proxy unset, API requests and WebSockets read those variables back and stayed on the old proxy until a reload. They now see only the environment VS Code started with. (#1163, fixes #1162)

Improvements

• Full session ID in the Coder output channel. Lines start with [client_session_id=<id>] instead of [session <first 8 characters>], the same key the coder CLI, the agent, and JetBrains Toolbox log. (#1164)

Note

The npm_config_proxy, npm_config_http_proxy, npm_config_https_proxy, and npm_config_no_proxy variables are no longer read. Use http.proxy and http.noProxy, or HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. (#1163)

Full changelog: v1.17.1...v1.17.2