How to run GitHub Copilot agent sessions across any device | GitHub Copilot Day
Patrick Nikoletich explains how GitHub Copilot agent sessions can move between devices using GitHub’s shared agent runtime, the Copilot SDK, and the Agent Host Protocol, including a live demo that hosts an agent on a home Linux machine and connects to it from the Copilot CLI.
Overview
The video focuses on making Copilot agent sessions portable across different environments (editors, terminals, and devices) by separating the agent runtime from any single client.
What problem this addresses
- Agent sessions shouldn’t be tied to one specific code editor or one terminal window.
- Developers may want to:
- Start a session in one place (for example, a terminal)
- Continue it elsewhere (another device or client)
- Attach multiple clients to the same running session
Core building blocks discussed
- GitHub shared agent runtime: A runtime intended to allow an agent session to persist independently of a single client.
- Copilot SDK: SDK used to build or host Copilot-related agent experiences.
- Agent Host Protocol (AHP): Protocol intended to let different clients connect to and interact with a hosted agent session.
Demo highlights (from the provided timestamps/description)
- Demo environment uses a home network setup with Tailscale.
- The presenter shows:
- AHP clients and a service referred to as copilotd
- Spinning up an agent host on a Linux machine
- Connecting to that host from the GitHub Copilot CLI
- Bridging a local CLI to a home machine
- Starting a remote session and then attaching multiple clients
- Seeing live updates synchronized across clients
How to try it
The description includes links to:
- HydraFusion: https://gh.io/ghcpdayhydrafusion
- Copilot app: https://gh.io/ghcpdaycopilotapp
- Copilot app resources: https://gh.io/ghcpdaycopilotappresources
- GitHub Copilot CLI install: https://gh.io/ghcpdaycopilotcli
- Copilot Dev Days: https://gh.io/join-dev-days