# VS Code is moving coding agents into a standalone host with shared AHP sessions VS Code’s Agent Host moves Copilot, Claude and Codex sessions out of the extension host and into an independent process governed by the open Agent Host Protocol, so sessions can survive editor windows, be shared across clients and run beside remote workspaces. Microsoft is rearchitecting VS Code around a dedicated Agent Host rather than treating each coding agent as an editor-bound extension. AHP gives different harnesses one shared session model, but the rollout is still active and VS Code 1.132 removed the administrator policy that had centrally disabled the Agent Host. - Status: Active - Published: 2026-08-27T08:56:42+12:00 - Updated: 2026-08-27T08:56:42+12:00 - Categories: Artificial Intelligence, Web Development, AI Agents, AI Coding, Developer Tools - Tags: Agent Host Protocol, Claude, Codex, Coding agents, Copilot, VS Code - Canonical HTML: https://beyondthe.news/dossiers/vs-code-agent-host-ahp-shared-remote-coding-agent-sessions ## What changed Microsoft is progressively moving VS Code agent sessions into a dedicated Agent Host process. The host runs adapters for coding-agent harnesses such as Copilot, Claude and Codex and communicates with editor clients through the open Agent Host Protocol (AHP), a JSON-RPC protocol with synchronized session state. Unlike the older extension-host model, the Agent Host owns the session independently of any particular VS Code window: multiple clients can observe the same session, remote hosts can run beside the workspace, and active work can continue when no editor client is connected. VS Code 1.130 made the architecture a prominent rollout feature, and 1.132 continued the rollout while removing the `ChatAgentHostEnabled` enterprise policy that previously allowed administrators to centrally disable it. ## Why it matters The architecture changes what an IDE coding agent is. Instead of being a feature whose lifecycle is tied to one editor window, it becomes a long-running workspace service that clients can connect to and leave. That makes persistent and remote agent work more practical and lets multiple harnesses share common session concepts, but it also changes governance and extension assumptions. Agent work can continue after a window closes, edits occur directly in worktrees/session folders, extension-provided tools may exist only while a contributing client is connected, and administrators no longer have the removed central Agent Host policy as a blanket off switch. ## The agent session now belongs to the host, not the window VS Code documents the Agent Host as the source of truth for agent sessions. A client subscribes to session, chat, terminal and changeset state, receiving an initial snapshot followed by ordered actions. Because that state lives in the host, a developer can close one window, reconnect from another and keep the same session; an active turn can continue while no client is connected as long as the host keeps running. ## AHP creates a common layer across Copilot, Claude and Codex First-party adapters translate individual agent runtimes into the Agent Host Protocol’s common session model. AHP uses JSON-RPC and can operate locally or over WebSocket for remote hosts. That gives VS Code one client architecture for several harnesses instead of building separate lifecycle, reconnect and state-synchronization behavior around each agent implementation. ## Remote hosting moves execution next to the code The Agent Host can run as a standalone process beside a remote workspace. VS Code can reach it over SSH or a dev tunnel, while file edits and commands execute on the remote machine. The `code agent host` command can start a standalone host. This is closer to a persistent development worker than a normal chat extension and is relevant for long-running coding jobs that should continue without a laptop window remaining open. ## Extension tools and MCP need a different mental model The Agent Host is designed to be self-contained, but connected clients can contribute tools. Extension-provided tools are generally available only while an editor window running that extension is connected. MCP configuration also differs: the Agent Host reads harness-agnostic `.mcp.json` and user configuration, while VS Code forwards compatible servers configured through the client. Builders of extensions and team workflows should test which capabilities survive disconnects rather than assuming every editor extension follows the remote session automatically. ## Enterprise control has shifted during the rollout VS Code 1.132 removed the `ChatAgentHostEnabled` policy, explicitly stating that administrators can no longer centrally disable the Agent Host through that policy. Individual developers can still use `chat.agentHost.enabled` to choose whether agents run in the separate process. Organizations with AI-control requirements therefore need to review what other Copilot, agent, network and extension policies remain available instead of relying on the retired switch. ## Key details - The Agent Host is a dedicated process that owns agent sessions independently of VS Code clients. - First-party Agent Host adapters support harnesses including Copilot, Claude and Codex. - Agent Host Protocol is an open agent-agnostic JSON-RPC protocol with synchronized immutable session state. - Sessions can be connected to from multiple VS Code windows and can continue running without a connected client. - The Agent Host can run locally or as a standalone remote server next to the workspace; VS Code can connect over SSH or dev tunnels. - VS Code 1.130 highlighted the Agent Host rollout on July 22, 2026. - VS Code 1.132, released August 5, removed the `ChatAgentHostEnabled` enterprise policy, so administrators can no longer centrally disable the Agent Host through that policy. - Extension-contributed tools can depend on an editor client remaining connected, while the core host session is designed to operate independently. ## Builder takeaways - Treat Agent Host sessions as stateful development workers rather than transient chat tabs: define cleanup, worktree and review practices for sessions that outlive editor windows. - If repeatability matters, record which harness and Agent Host configuration produced a change; the common session layer does not make Copilot, Claude and Codex behavior identical. - Test which MCP servers and extension tools remain available when a developer disconnects before relying on unattended remote sessions. - Review generated diffs and commits carefully because Agent Host sessions apply edits directly in their session folder or worktree rather than keeping the older extension-host pending-edit model. - Enterprise teams should re-audit their AI policy controls after VS Code 1.132 because the dedicated Agent Host can no longer be centrally disabled through the removed `ChatAgentHostEnabled` policy. - Expose remote Agent Hosts only through authenticated SSH/dev-tunnel paths and keep connection tokens and workspace permissions scoped to the task. ## What to watch - When Microsoft considers the Agent Host and AHP stable rather than under active development. - Whether AHP gains adoption outside VS Code or becomes a broader interoperability layer for coding-agent clients and hosts. - How enterprise administrators replace the removed Agent Host disable policy where centralized prohibition is required. - Whether extension APIs evolve so client-provided tools can run reliably in headless or disconnected Agent Host sessions. - How session migration and compatibility work when Agent Host implementations or harness versions change. ## Uncertainties - Microsoft says the Agent Host and AHP remain under active development and capabilities are still progressively rolling out. - Feature behavior differs between Agent Host and legacy extension-host sessions, and older sessions can continue on the extension host. - A common protocol normalizes session mechanics but does not guarantee equivalent tool support, safety behavior or output quality across different agent harnesses. - The removal of one central policy does not mean organizations lack all Copilot or agent governance controls; the complete effective control surface depends on their VS Code and GitHub configuration. ## Sources - [VS Code Agent Host architecture](https://code.visualstudio.com/docs/agents/concepts/agent-host) — Microsoft / Visual Studio Code · primary architecture documentation · 2026-08-05T00:00:00+12:00. Defines the dedicated process, independent/shared sessions, AHP, local/remote hosting, tool behavior and differences from extension-host sessions. - [Visual Studio Code 1.130](https://code.visualstudio.com/updates/v1_130) — Microsoft / Visual Studio Code · primary release notes · 2026-07-22T00:00:00+12:00. Major rollout milestone for Agent Host, Copilot/Claude/Codex harnesses, shared windows, assisted permissions and worktree support. - [Visual Studio Code 1.132](https://code.visualstudio.com/updates/v1_132/) — Microsoft / Visual Studio Code · primary release notes · 2026-08-05T00:00:00+12:00. Confirms continued Agent Host rollout and removal of the `ChatAgentHostEnabled` central administrator policy. - [Agent Host Protocol](https://microsoft.github.io/agent-host-protocol/) — Microsoft · primary protocol documentation. Open protocol definition for host/client session communication.