GitHub Copilot: Agents Window Runs Sessions in Local Dev Containers

GitHub CopilotSep 16, 2026View original changelog

VS Code 1.138 lets GitHub Copilot's Agents window run an agent session inside a project's own local Dev Container instead of on the developer's machine directly, so the agent works with exactly the tools and dependencies the project defines. When the new chat.agentHost.devContainer.enabled setting is on, local folders with a supported Dev Container configuration surface a "Use Dev Container" action right from the folder menu, and Docker must be installed for it to run. GitHub is rolling the capability out gradually, so it may not be enabled by default yet, and developers can turn the setting on manually to try it early.

Key Takeaways

GitHub Copilot's Agents window can now run an agent session inside a project's local Dev Container instead of on the host machine.
The agent picks up the exact tools and dependencies the project defines, rather than whatever happens to be installed locally.
The capability is gated behind a new setting, chat.agentHost.devContainer.enabled, and applies only in the Agents window.
A supported folder shows a "Use Dev Container" action directly in its folder menu once the setting is turned on.
Docker must be installed on the developer's machine for a Dev Container session to run.
The feature is rolling out gradually, so developers who want it immediately can turn the setting on by hand rather than waiting.

Agent Sessions Get Their Own Environment

VS Code 1.138, released September 16, 2026, lets GitHub Copilot's Agents window run an agent session inside a local folder's Dev Container rather than directly on the developer's machine. Instead of relying on whatever tools and dependencies happen to be installed locally, the agent uses the exact environment configured for the project, keeping its work aligned with the project's own toolchain.

How It Works

The capability is controlled by a new setting, chat.agentHost.devContainer.enabled, and applies only within the Agents window. Once enabled, a local folder that has a supported Dev Container configuration automatically shows a folder menu with a "Use Dev Container" action; selecting it runs the agent session inside that folder's Dev Container. Docker must be installed on the developer's machine for the feature to work.

GitHub notes that local Dev Container sessions are rolling out gradually, so the setting may not be turned on by default for every user yet. Developers who want to try the feature immediately can enable the setting manually rather than waiting for it to roll out to their installation.