Integrate with agent frameworks

Orchestration frameworks such as LangGraph, Google ADK, Microsoft Agent Framework and CrewAI manage state, memory and control flow. a2a-wrapper does not replace them. It gives them execution nodes that are real coding agents.

LangGraph / ADK / Microsoft Agent Framework / CrewAI
        (state, memory, flow control)
                    ↓
              A2A protocol
                    ↓
   a2a-copilot · a2a-claude · a2a-codex · a2a-opencode · a2a-antigravity

What the orchestrator needs to doCopy Anchor Link

Any orchestrator that can make HTTP calls can drive a wrapper, in three steps:

1. Discover: GET {base}/.well-known/agent-card.json. Read url and skills.
2. Send: POST a message/send (or message/stream) JSON-RPC request to the card's url, reusing a contextId across turns.
3. Read: take the answer from the task's artifacts, and check status.state.

The quick start shows the exact requests, and the crew example shows a planner doing this against two agents.

Use an A2A client libraryCopy Anchor Link

If your framework or language has an A2A client, point it at the wrapper's base URL. The wrappers implement the standard protocol, so the official SDKs and inspectors work with them.

Two ways to compose agentsCopy Anchor Link

TipsCopy Anchor Link

• Reuse one contextId per agent per workflow so each agent keeps its own history.
• Give each agent its own workspace or branch if they edit files, to avoid conflicting changes.
• Use streaming (message/stream) for long tasks, or blocking calls with a generous timeout.
• Secure the wiring. Each agent is an unauthenticated entry point unless you add a gateway. See the security guide.