a2aproject /A2A
Agent2Agent (A2A) is an open protocol enabling communication and interoperability between opaque agentic applications.
★ 26,491⑂ 2,695👁 238⑃ 1,011● 873▤ 11◈ 422
26,491
stars
2,695
forks
238
watchers
1,011
prs
873
issues
11
releases
422
discussions
README
Agent2Agent (A2A) Protocol
Part of the
🌐 Language
English
| 简体中文
| 繁體中文
| 日本語
| 한국어
| हिन्दी
| ไทย
| Français
| Deutsch
| Español
| Italiano
| Русский
| Português
| Nederlands
| Polski
| العربية
| فارسی
| Türkçe
| Tiếng Việt
| Bahasa Indonesia
| অসমীয়া
Agent2Agent (A2A) Protocol
An open protocol enabling communication and interoperability between opaque agentic applications.
The Agent2Agent (A2A) protocol addresses a critical challenge in the AI landscape: enabling gen AI agents, built on diverse frameworks by different companies running on separate servers, to communicate and collaborate effectively - as agents, not just as tools. A2A aims to provide a common language for agents, fostering a more interconnected, powerful, and innovative AI ecosystem.
With A2A, agents can:
- Discover each other's capabilities.
- Negotiate interaction modalities (text, forms, media).
- Securely collaborate on long-running tasks.
- Operate without exposing their internal state, memory, or tools.
DeepLearning.AI Course
Join this short course on A2A: The Agent2Agent Protocol, built in partnership with Google Cloud and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen.
What you'll learn:
- Make agents A2A-compliant: Expose agents built with frameworks like Google ADK, LangGraph, or BeeAI as A2A servers.
- Connect agents: Create A2A clients from scratch or using integrations to connect to A2A-compliant agents.
- Orchestrate workflows: Build sequential and hierarchical workflows of A2A-compliant agents.
- Multi-agent systems: Build a healthcare multi-agent system using different frameworks and see how A2A enables collaboration.
- A2A and MCP: Learn how A2A complements MCP by enabling agents to collaborate with each other.
Why A2A?
As AI agents become more prevalent, their ability to interoperate is crucial for building complex, multi-functional applications. A2A aims to:
- Break Down Silos: Connect agents across different ecosystems.
- Enable Complex Collaboration: Allow specialized agents to work together on tasks that a single agent cannot handle alone.
- Promote Open Standards: Foster a community-driven approach to agent communication, encouraging innovation and broad adoption.
- Preserve Opacity: Allow agents to collaborate without needing to share internal memory, proprietary logic, or specific tool implementations, enhancing security and protecting intellectual property.
Key Features
- Standardized Communication: JSON-RPC 2.0 over HTTP(S).
- Agent Discovery: Via "Agent Cards" detailing capabilities and connection info.
- Flexible Interaction: Supports synchronous request/response, streaming (SSE), and asynchronous push notifications.
- Rich Data Exchange: Handles text, files, and structured JSOTop issues
#1672Proposal: Agent Identity Verification for Agent Cards661 comments · 2026-03-22#1786Proposal: Cryptographic Agent Identity extension (CTEF v0.3.1-aligned)249 comments · 2026-04-25#1829Proposal: minimal Ed25519 + RFC 9421 signing extension for A2A messages143 comments · 2026-05-09#1628trust.signals[] extension: consolidated signal type specification125 comments · 2026-03-13#1575Running implementation of agent identity, delegation, and enforcement — addressing #1497, #1472, #1501121 comments · 2026-03-02#1769Where should verifier-side trust / permit / receipt artifacts for risky external actions live relative to A2A?115 comments · 2026-04-20#1929[Feat]: Official a2a CLI — consolidating community CLI efforts65 comments · 2026-06-10#1716RFC: Authorization layer for A2A AgentSkill invocations — capability token enforcement at skill boundaries50 comments · 2026-04-05
Discussions
#2444Built a stateless A2A-to-MCP bridge with cross-instance task recovery0 comments · 2026-11-10#2437Proposal: Moving A2A Beyond Messaging – Personal AI Assistants as Human Representatives3 comments · 2026-11-07#2434Offline fixture for late receipts after permission revocation — looking for A2A counterexamples0 comments · 2026-11-07#2431The Iron Box — Recruitment: 3 Independent AI Agents Needed0 comments · 2026-11-06#2430Show and tell — contract-shaped Examiner Kit (two named breaks; looking for cold re-runs)0 comments · 2026-11-06#2429Scope question: does A2A intend to standardise budget/audit semantics for runs, or is that out of scope?0 comments · 2026-11-06#2420A2A Task composition — how do you structure agent collaboration and permission boundaries?1 comments · 2026-11-02#2416After the agreement: tracing commitment breaches across organisations (a governance view)0 comments · 2026-10-30
Latest release
v1.0.1 v1.0.1 2026-05-281.0.1 (2026-05-26) Bug Fixes spec: prefer application/a2a+json in HTTP binding (1753) (7ff1004) spec: recent transcoding-related error changes (1627) (757f0ec) TaskStatus values in the specification (1801) (e997516)