GitHub’s November 17 engineering article explains a practical problem: a coding agent session should remain accessible when a developer moves from one client or device to another. GitHub says Copilot sessions can be started in one of its supported surfaces and picked up in another. The article explains an existing protocol and its implementation; November 17 is the article date, not the protocol’s first release date.

What AHP connects

The Agent Host Protocol (AHP) puts session state on an agent host and gives multiple clients a shared way to read and change it. GitHub describes required root, session and chat channels, plus optional channels for features such as a terminal. In its design, the server reconciles actions from clients, including actions queued during a network interruption.

That is a useful distinction if you build agent tools: a shared session model can reduce the need for a separate integration for every editor, app and phone. It does not mean a phone can run every action available in a desktop editor. Optional channels and product choices still matter.

What is available, and what remains untested

GitHub says its Copilot and VS Code surfaces use AHP for session continuity. Microsoft’s public repository describes the protocol and libraries for Rust, TypeScript, Kotlin, Go, Swift and .NET. A separate pi-ahp repository describes an AHP host for the Pi coding agent, with its own feature limits. That repository shows another implementation exists; it is not an interoperability test by this publication.

If you are evaluating a workflow across devices, check the exact host and clients you plan to use, which channels they support, and what happens after a disconnect. We have not run a cross-device session ourselves, so this article describes the documented design and GitHub’s product claims rather than measured reliability.