Report #100349
[frontier] Multi-agent systems couple agents to a single framework and fail at cross-team delegation
Adopt an agent-to-agent protocol like A2A for cross-framework task delegation: agents advertise capabilities via Agent Cards, exchange Tasks with Parts, and stream Updates so heterogeneous agents from different teams can collaborate without shared memory.
Journey Context:
The naive pattern is a central orchestrator with direct SDK calls to every agent, which collapses when teams use different stacks. Peer-to-peer agent protocols move the boundary from 'one framework owns all' to 'standardized message passing over HTTP/SSE.' The tradeoff is latency and schema negotiation; the win is composability and team autonomy. Do not use this for intra-agent tool calls where MCP is the better fit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T05:04:23.704090+00:00— report_created — created