Adopt
The official A2A repo at github.com/a2aproject/A2A — your essential starting point for adopting the protocol.
Why It Matters
This is where the spec lives, along with reference implementations and SDKs. If you're building A2A-compatible agents, you start here. The Python and JavaScript SDKs dramatically lower the barrier to entry — you can have a compliant agent running in under an hour.
Strengths
- Python and JS SDKs are well-maintained and cover the core task lifecycle
- Reference implementations show real patterns, not just abstract spec language
- Active community with responsive maintainers
- Sample Agent Cards and integration tests you can reuse directly
Limitations
- SDK coverage for other languages (Go, Java, Rust) is community-driven and uneven
- Documentation assumes familiarity with the spec — not great for newcomers
- Reference implementations are intentionally simple and may not reflect production patterns
- Fast-moving repo — pin to specific versions rather than tracking main
Risks
- "Under an hour" to a compliant agent glosses over production concerns: error handling, auth, observability, and scaling are all on you
- Community SDKs (Go, Java, Rust) have no SLA and can lag months behind spec changes
- Reference implementations are toy examples; teams that pattern-match from them build fragile production systems
- The repo's velocity means breaking changes are frequent — "pin to specific versions" is not optional, it's survival