What happened
In an October 28, 2026 changelog post, GitHub described a set of GitHub Copilot updates for Visual Studio Code. The headline workflow is cloud-session continuity: a user can start a cloud agent session from the Agents window in VS Code, then find and continue that same session in VS Code, the GitHub Copilot app, GitHub Mobile, github.com, or Copilot CLI. GitHub says the agent runs on its infrastructure, so closing the laptop does not stop the work. Sessions started in a Slack or Microsoft Teams direct message can also be continued in those clients. The post does not give a price or rollout limit for these capabilities.
The release also distinguishes this cloud workflow from agents that run on a developer’s own machines. A new Agent Host isolates Copilot sessions from individual VS Code windows, allowing work to continue after the project folder or window is closed. Developers can run agents on a separate machine and use Remote SSH or dev tunnels to access it through the Agents window. The remote agent uses the same code, tools, and dependencies, but the remote machine and its Agent Host must remain running. Another local workflow lets users control an agent on their development machine from GitHub Mobile; setup requires opening a terminal in the project folder and running code agent host --github-environment.
GitHub says the Copilot harness, built on the Microsoft Copilot SDK, is now the default for new sessions in both the editor and Agents window, with the stated aim of more consistent behavior across VS Code, Copilot CLI, and the GitHub Copilot app. The Agents window can also run models and harnesses in parallel on the same coding task, show results side by side, ask a Judge model to recommend an approach, and use Synthesize to combine ideas. GitHub labels this comparison capability a preview.
The open Agent Host Protocol (AHP) is the release’s extensibility piece. GitHub says developers can build clients that connect to an Agent Host and use the same live sessions as VS Code; clients can stay in sync and catch up after reconnecting. It lists client libraries for TypeScript, Rust, Go, Kotlin, and Swift. The changelog also describes computer use, an experimental feature that lets Copilot interact with desktop apps after users enable it in settings and run /computer on. Each application requires approval, organizations can disable the feature by policy, and the same setup is shared with Copilot CLI and the GitHub Copilot app.
What the archive adds
This is a new release in a continuing Copilot story, not a restatement of the prior model and CLI updates in our October 28 Copilot CLI note. The archive also records that GitHub’s Copilot CLI gained Agent Client Protocol support in January, while this changelog introduces AHP for clients connected to Agent Host. The related earlier Telegram post is a separate protocol development, not evidence that the two protocols are interchangeable.
Trend signal
This release supports the pattern that protocols are becoming an interoperability layer: agent protocols become the interoperability layer. AHP is presented as an open way for third-party clients to connect to GitHub’s Agent Host and keep session state synchronized across reconnects. One vendor announcement does not establish broad adoption, but it makes the integration boundary concrete: clients can be built around a running agent session rather than only around a particular editor view.
Why now
GitHub frames the release around choice in models, where agents run, and how users stay involved. Its specific workflow examples—starting work from a phone, steering it at a desk, and checking it later on the web—explain the timing as an effort to make ongoing agent work fit between devices and clients. The source does not tie the announcement to a market deadline or external event.
Connections to other events
Earlier coverage in the archive described GitHub’s Agent HQ announcement, which positioned GitHub as a place to orchestrate agents from multiple providers. The current release is narrower and more operational: it explains how Copilot sessions persist across clients and how other clients can attach to an Agent Host. The January Copilot CLI ACP update is another protocol development in the same broader story of agent workflows crossing interfaces; the changelog does not claim AHP replaces ACP.
Why it matters
For teams already using Copilot, the useful shift is that a coding task need not be tied to one editor window or one device. A cloud session can keep running while a developer changes context, and a mobile or web client can be used to check in. For local and remote agents, the persistence model is different: the machine hosting Agent Host must stay up. That distinction matters when teams plan unattended work, machine availability, and handoffs.
AHP may matter to teams building internal developer tools or alternative interfaces around Copilot sessions. Instead of treating VS Code as the only control surface, a team can investigate a client that connects to Agent Host using one of the listed language libraries. The announcement establishes the intended capability, not the maturity of every library or the degree of access custom clients receive. The preview comparison feature and experimental computer use also need to be evaluated separately from the generally described session workflows; they carry preview or experimental status and, for desktop interaction, explicit approval and policy controls.
What happens next
- Third-party clients will begin using AHP to continue Copilot sessions outside GitHub’s listed clients (6 months, 55%). Watch for: documented client examples or public projects using the protocol.
Limits and uncertainty
The changelog does not specify AHP’s protocol version, license, compatibility guarantees, or whether third-party clients have the same capabilities as GitHub’s own clients. It gives no pricing, availability schedule, usage limits, or account-plan requirements for session continuity. Cloud sessions run on GitHub infrastructure, while local and remote workflows have explicit machine-running requirements; the source does not compare their reliability or cost. The parallel model comparison is in preview, and computer use is experimental. The announcement also does not provide benchmarks showing that the default harness improves output quality, nor evidence of adoption by external client builders.
Skill to build now
Map one existing Copilot task across the surfaces your team already uses: start a cloud session, continue it from another supported client, and record what context and controls persist. Separately test the local workflow only on a machine your team can keep running. This gives a practical baseline before designing around AHP or assuming that cloud and machine-hosted sessions behave the same way.
Reader takeaway
GitHub is making Copilot sessions more continuous across clients and opening a protocol for custom Agent Host clients. The practical opportunity is to let work outlive a particular editor or device; the operational caveat is to distinguish GitHub-hosted sessions from agents that depend on a running machine. Treat AHP as a newly announced integration surface, not proof yet of a mature multi-vendor standard.