The Pulse
GitHub details protocol for Copilot sessions across devices
GitHub says its Agent Host Protocol lets Copilot agent sessions continue across editors, apps and devices. The open protocol has separate VS Code and GitHub host implementations, with libraries available in six programming languages.

GitHub Copilot agent sessions can continue across apps and devices using a shared protocol, rather than being tied to a single editor window. GitHub says the Agent Host Protocol, developed first in VS Code and adopted across its products, provides that continuity for sessions running locally, in cloud sandboxes and in VS Code.
The company detailed the open protocol and its implementations in a November 17 engineering post. Developers can also use it to connect their own clients and agent hosts.
From separate integrations to shared sessions
GitHub previously built Copilot in VS Code as an extension with its own agent harness. The extension was attached to a VS Code window, so closing the window ended its agent; restarting the application for an update stopped agents too.
The Copilot app and GitHub mobile apps for iOS and Android each had their own integrations with cloud agents. The protocol was designed as an independently versioned way for clients to interact with the same agents, history and state without requiring a separate integration for each product.
For example, a user could start a cloud session from a phone and continue it from a laptop. The protocol was designed to handle interruptions, reconnections and changes from clients working at the same time.
How the protocol works
The protocol is organized around channels identified by URIs. Every server must support root, session and chat channels; servers can also implement channels for functions such as terminal support, MCP additions or telemetry reporting.
Each channel contains a state object based on reducers. The server determines the state, while clients send actions that can change it or trigger effects such as sending a chat message.
On reconnection, a client sends queued actions and waits for the server to reconcile and acknowledge them before confirming them. The protocol focuses on interactions with agents rather than encoding how the agents themselves work.
Two hosts and developer access
Supporting the protocol in VS Code required a new harness and agent stack. The Copilot Chat extension had grown to more than 400,000 lines of TypeScript, excluding tests, but was structured around the lifetime of a VS Code window and relied on its extension API.
Work on the protocol began in early 2026, as the Copilot SDK was also being developed. GitHub says it made sense to use the SDK as the foundation for the new agent stack.
VS Code and GitHub have separate agent host implementations, written in TypeScript and Rust respectively. The VS Code host runs locally and can run on other compute through connections including SSH, containers, WSL or Dev Tunnels; the GitHub host needed to run in the cloud across a wider variety of infrastructure and security constraints.
In comparing the implementations, the engineers found both product-specific extensions and gaps in the protocol. Early versions, for example, could not accurately represent shell-type tool output that was not backed by a PTY.
Libraries for the protocol are available in Rust, TypeScript, Kotlin, Swift,.NET and Go. In the Copilot app, developers can connect an agent host they implement by enabling Direct Connections under Experimental settings and then adding an Agent Host Protocol host under Environments.
VS Code offers an Add Remote Agent Host option in its Agents window. Developers can also start a standalone version of its agent host from a terminal with code agent host, or inspect the editor host’s endpoints with code agent endpoints.