In the VS Code Insiders podcast, Connor Peet explains the Agent Host Protocol, a new open communication system designed to manage long-lived AI agent sessions across multiple devices and clients within VS Code, enhancing flexibility beyond the traditional single-window model. The protocol enables seamless state synchronization, multi-client interaction, and advanced orchestration of AI agents, with ongoing development inviting community contributions to expand its capabilities and integrations.
In this episode of the VS Code Insiders podcast, host James Monte Magno interviews Connor Peet, a long-time member of the VS Code team, about the Agent Host Protocol—a new and evolving system designed to enhance how AI agents and sessions are managed within VS Code. Connor shares his background, highlighting his recent work on AI-related features and the development of the Agent Host Protocol, which aims to improve the flexibility and longevity of agent sessions beyond the traditional single-window, local process model.
Connor explains the evolution of agent sessions in VS Code, starting from local agents running within a single VS Code window to the introduction of the Agent Window, which allows users to manage multiple agent sessions across different folders and workspaces. The key challenge addressed by the Agent Host Protocol is enabling long-lived agent sessions that can persist independently of any open VS Code window, supporting scenarios where agents run for extended periods and can be accessed from multiple devices or clients.
The Agent Host Protocol is designed as an open, standardized communication protocol, similar in spirit to the Debug Adapter Protocol and Language Server Protocol. It allows different clients and servers to interact seamlessly, enabling developers to build custom tools and interfaces that connect to agent sessions regardless of where or how they are hosted. Connor highlights that VS Code already supports this protocol, and third-party developers can create their own clients or harnesses, including mobile apps or integrations with devices like Stream Deck, to monitor and interact with agent sessions.
A significant aspect of the protocol is its ability to synchronize state across multiple clients and handle complex scenarios such as disconnections, reconnections, and multi-machine coordination. Connor also distinguishes the Agent Host Protocol from the Agent Client Protocol, noting that while the latter controls individual harnesses, the former manages higher-level orchestration and state synchronization across distributed systems. This layered approach opens up possibilities for richer orchestration of AI agents, including multi-chat sessions and automated workflows.
Looking ahead, Connor envisions the Agent Host Protocol enabling advanced orchestration features, such as scripting custom workflows and integrating with various extension APIs to create highly personalized and automated development experiences. The protocol is still in active development and open source, inviting community contributions and experimentation. Connor encourages developers to get involved by exploring the GitHub repository, submitting issues, and building new integrations, emphasizing the protocol’s potential to transform how developers interact with AI agents across the VS Code ecosystem and beyond.