Releases: coder/vscode-coder
v1.14.4-pre
Added
coder.binaryDestinationnow accepts a full file path (e.g./usr/bin/coder) in addition to a directory. The extension checks the binary's version against the server and downloads a replacement when needed. When set to a directory, the simple name (coder/coder.exe) is tried as a fallback after the platform-specific name, so package-manager-installed CLIs work without symlinking.- New Coder: Speed Test Workspace command to run
coder speedtestfrom the command palette or workspace sidebar. Choose a running workspace, optionally set the test duration, and open the JSON results directly in VS Code. - New Coder: Ping Workspace command to run
coder pingfrom the command palette or workspace sidebar, with live connectivity diagnostics in a terminal. - New Coder: Create Support Bundle command to run
coder support bundlefrom VS Code and save the resulting diagnostics zip for troubleshooting. Available when your deployment supports support bundles. - Coder SSH connections now default to
ServerAliveInterval=10andServerAliveCountMax=3, helping keep sessions alive through NATs and firewalls while detecting dead connections within about 30 seconds. - New
coder.networkThreshold.latencyMssetting (default: 250ms, set to0to disable) to warn when workspace latency stays high. The network status bar indicator turns yellow and offers quick actions to run Coder: Ping Workspace or open the setting.
Fixed
- Cleanup of old/temp files in shared directories like
/usr/binis now scoped to the binary's own basename, preventing accidental removal of unrelated files. - The Coder: Update Workspace flow now goes through the normal startup path for more reliable updates and restarts, and reconnecting to a stopped outdated workspace now offers Start or Update and Start.
- Outdated workspace notifications are now deferred until setup completes, so they no longer appear during an in-progress update.
- Workspace build logs now reliably appear in the Coder: Workspace Build output channel during startup.
v1.14.3
This release brings embedded AI agent chat, smarter SSH connection handling, flexible notification controls, and a batch of reliability improvements.
Highlights
Coder Chat: Talk to AI Agents Without Leaving Your Editor
Delegate development tasks to Coder's AI coding agents directly from VS Code's secondary sidebar. Describe what you need and the agent handles provisioning, execution, and follow-up, all without switching windows. (#844)
- Theme-aware panel that matches your VS Code color scheme
- Opens external links natively
- Only visible when the Agents experiment is enabled on your deployment
Note
Requires Coder Agents (Early Access) to be enabled. To use the chat panel, open a conversation from the Coder web UI first.
OS Keyring Support (Opt-In · macOS & Windows)
Session tokens can now be stored in your operating system's keyring via the Coder CLI, keeping credentials in sync between VS Code and the terminal. (#816, #835)
- Opt-in via the
coder.useKeyringsetting - Tokens are saved at login time, not just when connecting to a workspace, so the CLI can use them immediately
--use-keyringand--global-configare automatically filtered from user-configured global CLI flags to prevent auth conflicts
Important
macOS and Windows only. Requires Coder CLI >= 2.29.0 (storage) and >= 2.31.0 (full sync).
SSH Configuration Improvements
coder config-sshoptions honored: SSH options set viacoder config-ssh --ssh-option(e.g.ForwardX11=yes) are now applied to VS Code connections automatically. (#833)- Proxy log directory auto-configured: SSH connection logs are always captured in the extension's storage, no manual setup needed. Also respects
CODER_SSH_LOG_DIR. (#827)
Improvements
Silence Deployment Notifications
New coder.disableNotifications setting lets you suppress all notification prompts from your Coder deployment, including workspace update reminders, autostop warnings, deletion alerts, and inbox messages. Toggle it back on at any time without a reload. (#853)
Smarter SSH Reconnection Defaults
The extension now automatically configures reconnectionGraceTime, serverShutdownTimeout, and maxReconnectionAttempts with safe defaults that improve on VS Code's out-of-the-box values. For more aggressive (but still recommended) values, run Coder: Apply Recommended SSH Settings from the command palette to overwrite all settings at once. (#826)
Tip
Results may vary depending on your environment and network conditions. If you still experience disconnects, please open an issue.
Bug Fixes
- SSH sleep/wake recovery and process discovery: Connections now recover faster after laptop sleep by detecting port changes and re-registering the label formatter. Process discovery now uses
ss→netstat→lsofon Linux andnetstat→lsofon macOS, fixing systems where the SSH PID could not be resolved. (#846) - Windows SSH config writes: Fixed failures when antivirus, cloud sync, or another process briefly locks the SSH config file (retries on
EPERM/EACCES/EBUSY). (#841) - RemoteCommand compatibility: SSH connections no longer fail when a custom
RemoteCommandis configured. (#854) - URI handler fix: Opening a workspace via URI without a
folderparameter now correctly opens a bare remote window instead of falling back toexpanded_directory. (#865) - Cursor compatibility: Tasks view container now shows correctly in Cursor when not authenticated. (#839)
Breaking Changes
Warning
Minimum VS Code version is now 1.106.0 (uses Electron 37 / Node 22).
New Contributors
- @ThomasK33 — Coder Chat panel implementation
Full changelog: v1.13.2...v1.14.3
v1.14.2-pre
Added
- Coder Chat panel: delegate development tasks to AI coding agents directly from VS Code's sidebar. Describe a task and the agent handles workspace provisioning and execution automatically. Requires [Coder Agents](https://coder.com/docs/ai-coder/agents (Early Access) to be enabled on your deployment.
- New
coder.disableNotificationssetting to suppress all notification prompts from the Coder deployment, including workspace update reminders and scheduling alerts.
Fixed
- Fixed SSH connections failing when a custom
RemoteCommandis configured in SSH config. - SSH connections now recover faster after laptop sleep/wake by detecting port changes and re-registering the label formatter.
- SSH process discovery now uses
ss->netstat->lsofon Linux andnetstat->lsofon macOS, fixing systems wherenetstatwas unavailable and the SSH PID could not be resolved, which broke network info display and log viewing.
Changed
- Breaking: Minimum VS Code version is now 1.106.0.
v1.14.1-pre
Added
- Automatically set
reconnectionGraceTime,serverShutdownTimeout, andmaxReconnectionAttempts
on first connection to prevent disconnects during overnight workspace sleep. - New Coder: Apply Recommended SSH Settings command to overwrite all recommended SSH settings at once.
- Proxy log directory now defaults to the extension's global storage when
coder.proxyLogDirectory
is not set, so SSH connection logs are always captured without manual configuration. Also respects
theCODER_SSH_LOG_DIRenvironment variable as a fallback. - SSH options from
coder config-ssh --ssh-optionare now applied to VS Code connections,
with priority order: VS Code setting >coder config-sshoptions > deployment config.
Fixed
- Fixed SSH config writes failing on Windows when antivirus, cloud sync software,
or another process briefly locks the file. - Fixed Tasks view container not showing in Cursor when not authenticated.
Changed
coder.useKeyringis now opt-in (default: false). Keyring storage requires CLI >= 2.29.0 for
storage and logout sync, and >= 2.31.0 for syncing login from CLI to VS Code.- Session tokens are now saved to the OS keyring at login time (when enabled and CLI >= 2.29.0),
not only when connecting to a workspace.
Note
Sync requires Coder v2.31+ as it depends on the coder login token command, which is not available in earlier versions.
v1.14.0-pre
Added
- Re-introduced OS keyring support for session tokens (reverted in v1.13.2), now delegating to the Coder CLI instead of native
@napi-rs/keyringbinaries. This keeps the credential format in sync with the CLI automatically.
Note
Sync requires Coder v2.31+ as it depends on the coder login token command, which is not available in earlier versions.
Fixed
--use-keyringand--global-configare now explicitly filtered from user-configured global CLI flags to prevent conflicts with the extension's auth mode.
v1.13.2
Fixed
- Removed OS Keyring behavior changes
v1.13.1
Added
- Session tokens are now stored in the OS keyring (Keychain on macOS, Credential Manager on Windows) instead of plaintext files, when using CLI >= 2.29.0. Falls back to file storage on Linux, older CLIs, or if the keyring write fails. Controlled via the
coder.useKeyringsetting.
Fixed
- Fixed CLI binary downloads failing when servers or proxies compress responses unexpectedly.
- Clarified CLI download progress notification wording.
v1.13.0
Added
- Tasks panel: a new sidebar panel to create, view, and manage AI tasks directly from VS Code. Includes a task list with status indicators, a detail view with chat-style log streaming and real-time workspace build logs, and the ability to send messages or pause the agent without leaving the editor.
- New "Switch Deployment" command to change deployments without clearing credentials.
- New "Manage Credentials" command to view and remove stored credentials for individual deployments.
Changed
- Logout now clears stored credentials for the current deployment.
- The workspace update confirmation button now reads "Update and Restart" to clarify that updating will restart the workspace.
v1.12.2
Added
- Support for VS Code's built-in proxy settings:
http.noProxy(as fallback whencoder.proxyBypassis not set),http.proxyAuthorization, andhttp.proxyStrictSSL.
Fixed
- Fixed proxy scheme handling where URLs with schemes got duplicated and URLs without schemes were not normalized.
Changed
- WebSocket connections are now more robust and reconnect less frequently, only when truly necessary, reducing unnecessary disconnections and improving stability.
v1.12.1
Fixed
- Fixed GPG signature verification failing when public keys have been reformatted.
- Fixed race conditions when multiple VS Code windows access deployments simultaneously.
Changed
- Refined logging with clearer messages and more accurate severity levels for easier troubleshooting.



