An interoperability protocol standardizes how components exchange context across system boundaries. It provides a shared representation for capabilities, messages, state, tasks, artifacts, and events when components cannot share in-memory state or pass function arguments directly. section 7.8
Unlike coordination patterns within one application, protocols support collaboration across processes, services, frameworks, or organizations. For example, a support assistant may need to consult a billing agent reachable only through an external system. section 7.8
Table 7.3 Interoperability protocols, compared by the boundary each one crosses, the context exchanged across that boundary, and the primary use case
| Protocol | Boundary | Context exchanged | Primary use case |
A2A |
Agent to agent |
Capability cards, task messages, conversational identifiers, and structured artifacts |
Task delegation and structured context sharing between independent agents |
AG-UI |
Agent to user interface |
Real-time execution events, generative UI schemas, and synchronized client state |
User interaction, streaming feedback, and human-in-the-loop context injection |
ACP |
Editor to coding agent |
Workspace file trees, code diffs, terminal outputs, and permission grants |
Standardized IDE integration and bi-directional context exchange for coding agents |
LSP |
Editor or agent to language tooling |
Semantic abstract syntax tree symbols, type definitions, references, and diagnostics |
Language-aware code intelligence without parsing raw source text directly |
Compare protocols by the boundaries they cross, the context they exchange, and their primary use cases. section 7.8
