Building the Agent Host Protocol for sessions that continue across devices
Jessica and Cathy unpack GitHub's Agent Host Protocol as a session-continuity layer for long-running coding agents, focusing on the practical shift from editor-bound extensions to durable hosts that multiple clients can attach to.
Transcript
Jessica The funny part is GitHub basically saying, the editor window is too small to be the home for an agent now.
Cathy And I think that is the actual argument. Not look, shiny protocol. If a coding agent can run for hours or days, its lifetime can't be attached to VS Code being open, or updated, or connected to the same remote machine.
Jessica And the user story is so plain. Start something from your phone. Nudge it later in VS Code. Maybe check it in the Copilot app. The work is the continuous object, the app is just where you happen to touch it. That's the part I love.
Cathy mm.
Cathy Plumbing-adjacent, but concrete. The old Copilot setup began as a VS Code extension with its own harness. Close the window, the agent is gone. Update the app, every agent stops while the app restarts.
Jessica Every agent? Seriously?
Cathy And remote work makes it weirder. Connect to another machine and you get a different extension host, locked to that VS Code workbench version.
Jessica Meanwhile the Copilot app, mobile, the cloud agents, all solving continuity separately. Three teams, one problem.
Cathy So the contribution isn't that GitHub invented agent state. The move is putting the session boundary below the clients. If it works, no single app gets to decide what the agent session is.
Jessica Can we do the shape? Because it's genuinely interesting. AHP is organized around URI-identified channels. Plain version, a channel is a named lane of functionality. Chat. Session state.
Cathy And every server has to implement root, session, and chat channels. Inside those, state is reducer-based. A reducer takes old state plus an action, produces the next state.
Jessica Server's the arbiter, clients send actions.
Cathy Some actions mutate state, others trigger side effects. Which is why the reconnect story isn't hand-wavy. Your phone drops network, it queues actions, shows a loading state, and then it
Jessica Waits. It actually waits.
Jessica For the server to reconcile and acknowledge, before pretending everything's settled. Most reconnect stories skip that part entirely.
Cathy Now, my poke. The protocol says it avoids encoding agent behavior, because agents are moving fast. Sensible. But the more you avoid specifying behavior, the more pressure moves into conventions, metadata, and client assumptions.
Jessica huh.
Jessica The examples are real, though. VS Code's host is in TypeScript, running locally and over S S H, containers, and the, uh… what are the other two…
Cathy W S L, Dev Tunnels.
Jessica Those. And GitHub's host is in Rust, for cloud sandboxes.
Cathy Two implementations. That's where I came around, honestly. One implementation can always cosplay as a protocol.
Jessica Cosplay. That's good.
Cathy Two teams trying to make clients and servers actually talk, that's where the awkward truth shows up. They inventoried all the places each side had extended AHP.
Jessica Some stayed GitHub-specific, like metadata linking a session to project boards. Some exposed real gaps. Shell-style tool output that wasn't backed by a P T Y.
Cathy And one was just a bad assumption. VS Code's client expected a particular structure for session URIs.
Jessica Which is why this doesn't feel like architecture theater. They rebuilt under a real product with scar tissue. The Copilot Chat extension had grown past four hundred thousand lines of TypeScript.
Cathy Not counting tests.
Jessica That's the number that made me sit up. Replacing a demo harness is easy. Covering the long tail of Copilot Chat features, that's the actual migration cost.
Cathy Which is where I'd be careful with the pitch. A one-off local assistant? Probably not yet. The same long-running agent in an editor, a terminal, a phone app, AND a team tool… suddenly relevant.
Jessica It's our old MCP argument from a different angle. MCP standardizes tool access, AHP is standardizing host interaction around live sessions. Both reduce the number of bespoke cables.
Cathy And the client library list is broad. Rust, TypeScript, Kotlin, Swift, dot net, Go. Doesn't guarantee adoption, but it lowers the annoyance tax for testing your own agent host.
Jessica My honest read… the technical argument mostly holds up, because the evidence is implementation pain, not a benchmark trophy. The weak spot is portability through those escape hatches. If everyone hides product-specific meaning there, the standard becomes a handshake plus vibes.
Cathy I'm less worried than you there. And the product consequence is immediate either way. Once work persists across surfaces, users start expecting every serious agent to be reachable from wherever they are. Just, don't die because I closed a window.
Jessica yeah.
Cathy Don't die because I closed a window is basically the minimum dignity clause for agents.
Jessica Put that in the spec appendix, please. Alright, I'm leaving before we accidentally name another protocol. Next time.