Skip to content

v1.15.1

Choose a tag to compare

@github-actions github-actions released this 26 Jun 19:43
· 59 commits to main since this release
v1.15.1
99745f5

A patch release that adds a Network Check command for diagnosing connectivity straight from the command palette, lets the extension share login state with the terminal coder CLI, and routes file-based credentials through coder login/logout. Workspace opens now log more diagnostics, and VS Code's proxy settings finally reach the coder ssh ProxyCommand.

Highlights

Network Check Command

A new Coder: Network Check command runs coder netcheck from the command palette or the My Workspaces view menu. The report opens in a panel with an overall health banner, any warnings, a connectivity summary (UDP, IPv4/IPv6, NAT mapping, hairpinning, port mapping), per-region DERP/STUN results with latencies, and local interfaces. A View JSON action exposes the raw output. When a slow connection is detected, the network status bar tooltip also links to the network check alongside the latency test, for a deployment-wide view of the network path. (#1002)

Coder: Network Check results panel

Shared Login With the Terminal CLI

Set --global-config=<dir> in coder.globalFlags to share login with the terminal coder CLI: the extension reads file-based CLI credentials from that directory, so logging in once works in both places. Requires a deployment on 2.31.0+. (#1011)

Improvements

Credentials Through coder login/logout

File-based credentials are now written and cleared through coder login and coder logout rather than by the extension directly. The minimum supported Coder version is now v0.25.0. (#1011)

More Diagnostic Logging on Workspace Opens

Workspace opens and coder:// URI handling now log more diagnostics (target workspace, agent, and handoff) to make failed opens easier to trace. URI parameter values, including tokens, are never logged. (#1015)

Bug Fixes

  • Proxy settings now reach SSH. VS Code's proxy settings (http.proxy, http.noProxy, and coder.proxyBypass) are propagated to the SSH environment as HTTP_PROXY/HTTPS_PROXY/NO_PROXY, so the coder ssh ProxyCommand connects through the configured proxy whether SSH runs as a child process or in a terminal. (#1012)

Full changelog: v1.15.0...v1.15.1