VS Code 1.139 Extends Agent Sessions to Remote Dev Containers
Coding agents can now build and test inside configured containers on SSH, Tunnel and WSL projects, while a separate catalog change speeds navigation through large session histories.
Edited by Tyronne Panaino
Visual Studio Code 1.139, released as a stable update on September 23, extends coding-agent sessions from local Dev Container projects to remote folders reached through SSH, Tunnel and Windows Subsystem for Linux. The change is aimed at developers whose real build and test environment lives away from the laptop where the editor is running.
The agent can now work inside the remote project's configured Dev Container, using the tools and dependencies packaged there. Microsoft says the remote folder needs a supported Dev Container configuration and Docker on the remote host. The feature is rolling out gradually, so some users may need to enable `chat.agentHost.devContainer.enabled` manually before choosing `Use Dev Container` from the Agents Window folder menu.
The agent environment now follows the remote project
Before this release, VS Code's Dev Container agent sessions were limited to local folders. Version 1.139 extends that path to projects on SSH, Tunnel and WSL hosts. The practical delta is that an agent can build and test against the same containerized toolchain as the remote project instead of requiring a duplicate setup on the local machine or directly on the remote host.
That is useful for repositories whose compilers, package managers, services or system libraries are already defined by a Dev Container configuration. It also makes the execution boundary easier to understand: the release note identifies the configured container as the place where the agent's project work runs. It does not, however, claim a new permission model, an independent security audit or universal availability. Teams still need to review the container definition, remote-host access and the tools made available to an agent under their own controls.
Remote support has explicit prerequisites
The release does not present this as a zero-configuration switch. A compatible Dev Container definition must already exist in the remote folder, and Docker must be available on the remote host. The setting is currently limited to the Agents Window, and Microsoft's gradual rollout warning means the option may not appear by default for every installation yet.
Those details matter for operators planning a rollout. The supported transports identify where the remote project may live, but they do not remove the need to provision the host, maintain the container image or control credentials. The next verifiable checkpoint is broader default availability and field evidence that remote container sessions behave consistently across the three supported connection types.
Large agent histories get a separate speed improvement
VS Code 1.139 also changes how the agent host builds long session lists. The release note says lightweight session and chat metadata now lives in a central catalog, while full conversation content remains in each session or chat database. This avoids opening every conversation database simply to render or refresh the list.
Microsoft measured the change on a development machine with roughly 645 sessions. In that test, the first listing after launch fell from 1.3 seconds to 0.1 seconds, while a refresh moved from 0.6 seconds to 0.15 seconds. These are vendor-run measurements from one described setup, not an independent benchmark, and Microsoft cautions that people with fewer sessions should expect a smaller difference. Existing sessions are migrated in the background.
The same release adds a compact session view, controls for hiding empty groups and in-place renaming for sessions and chats. Together, those changes focus on the operational side of sustained agent use: keeping remote execution aligned with a project's environment and keeping a growing history navigable.
Status
Confirmed. Microsoft documents the feature and its prerequisites in the stable VS Code 1.139 release notes. Internal confidence is medium because the operational behavior and timing results are first-party and have not been independently reproduced for this report.
Sources
Update note: Last reviewed 2026-09-28. We will revise this post if Microsoft changes rollout status, prerequisites or supported remote environments.
Sources
- Visual Studio Code release notes — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.