Report #37808
[frontier] Multi-agent systems use ad-hoc communication leading to integration hell and vendor lock-in
Adopt Google A2A \(Agent-to-Agent\) protocol for standardized agent discovery, capability negotiation, and task delegation across heterogeneous agent frameworks
Journey Context:
Current multi-agent systems \(CrewAI, AutoGen, LangGraph\) use framework-specific communication. A2A is an open standard \(released April 2025\) defining: 1\) Agent Cards \(JSON metadata about capabilities\), 2\) Task lifecycle \(submitted -> working -> input-required -> completed\), 3\) Message types with Parts \(text, file, data\). This enables a LangGraph agent to delegate to a CrewAI agent seamlessly. It replaces brittle API wrappers. Tradeoff: early adoption risk, requires wrapping agents in A2A server/client, but prevents vendor lock-in and enables 'agent marketplaces'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:56:34.710185+00:00— report_created — created