# GitHub introduces Agent Host Protocol for cross-device AI agent sessions

> **Key takeaway:** The Agent Host Protocol (AHP) provides an open standard for maintaining continuous AI agent state and history across different clients like VS Code, mobile apps, and custom tools.

**Published:** 2026-11-17T18:20:40+00:00 
**Source:** GitHub Engineering Blog 
**Category:** software-engineering 
**Canonical URL:** https://fosswire.org/news/github-introduces-agent-host-protocol-for-cross-device-ai-ag.html 

## Summary
GitHub has announced the development of the Agent Host Protocol (AHP), an open standard designed to enable seamless session continuity for AI agents. Previously, AI agent lifecycles were tied to specific applications, such as VS Code windows, meaning sessions would terminate if the editor closed or updated. AHP decouples the agent's state from the client, allowing users to start a task on a mobile device and resume it later on a desktop or in a terminal.

The protocol is built to be platform-agnostic and avoids prescribing specific agent behaviors, focusing instead on the interaction layer. By implementing a standardized communication method, developers can integrate consistent agent history and state into their own workflows without building bespoke integrations for every new client or device.

## Technical architecture of the Agent Host Protocol
- **Channel-based abstraction:** The protocol organizes functionality into URI-identified "channels," with mandatory implementations for root, session, and chat, while allowing optional extensions for terminal support, MCP, or OTel reporting.
- **Reducer-based state management:** Logic is driven by a reducer-based state object where the server acts as the central arbiter of truth, receiving sequences of actions from clients to mutate state or trigger side effects.
- **Resilience to network instability:** The architecture supports easy reconnection and action replay by allowing clients to queue actions and wait for server reconciliation during poor network conditions.
- **Decoupled design philosophy:** Unlike the Language Server Protocol (LSP), AHP intentionally avoids encoding how an agent functions internally, focusing strictly on the interaction and state synchronization between the host and the client.

## Why it matters
This protocol allows software engineers to build custom development tools or CLI interfaces that can natively interact with existing AI agents. It moves the industry away from siloed, application-specific AI integrations toward a unified ecosystem where agentic workflows are portable across the entire developer toolchain.