Community Hub
A2A is an open standard maintained by its community. It was originally developed by Google and donated to the Linux Foundation, and it is now a Growth Stage project at the Agentic AI Foundation (AAIF), maintained by a Technical Steering Committee (TSC). This hub gathers community entry points, news, and ecosystem integrations.
Join the community
- A2A Discord : chat with contributors, ask questions, and follow progress.
- GitHub Discussions and Issues : discuss protocol design, report problems, and propose improvements.
- Meetings and agenda: A2A meetings on the Linux Foundation platform and the TSC meeting agenda document .
- Project governance and maintainers: see GOVERNANCE.md and MAINTAINERS.md .
News and announcements
- What’s New in A2A Protocol v1.0
- A2A Protocol Ships v1.0: A Production-Ready Standard for Agent-to-Agent Communication
- A New Chapter for A2A: Joining the Agentic AI Foundation
- Introducing the A2A CLI
- A2A Extensions: Empowering Custom Agent Functionality (Google Developers Blog)
- A2A protocol: Demystifying Tasks vs Messages (Google developer community)
Use case highlights
- Multi-agent workflows: chain specialized agents together to automate complex processes, such as candidate sourcing for hiring or streamlining supply chain logistics.
- Agent marketplaces: build platforms where agents can discover and use the capabilities of agents from other providers.
- Cross-platform integration: let agents built on different frameworks, such as LangGraph and BeeAI, work together seamlessly.
- Evaluating multi-agent systems: use frameworks such as Vertex AI to assess the performance and success of collaborative agent trajectories.
Frameworks with built-in A2A integration
These agent frameworks ship A2A integrations, which makes it easy to get started:
- Agent Development Kit (ADK)
- Agno
- AG2
- BeeAI Framework
- CrewAI
- LangGraph
- LiteLLM
- Microsoft Agent Framework
- Pydantic AI
- Strands Agents
The full list is on the official community page .
SDKs
The project provides official SDKs in six languages; see Official SDKs . For languages the official SDKs do not cover (for example Swift, C++, PHP, and Elixir), community-maintained implementations are listed under Community SDKs on the official page. Listed SDKs must follow the specification, be published to a standard package registry, include documentation and CI-run tests, use the Apache 2.0 license, and be actively maintained.