A2acode

a2acode

Serve a coding agent over the [A2A](https://a2aprotocol.ai/) protocol. Other agents call it over A2A; it drives a real coding-agent session in your project — Claude Code, or any agent that speaks Zed's [Agent Client Protocol](https://agentclientprotocol.com) (ACP): Gemini CLI, Codex, OpenHands, and more — and streams the work back as it happens.

[](https://github.com/kanywst/a2acode/actions/workflows/ci.yml) [](LICENSE) [](https://www.python.org/) [](https://a2aprotocol.ai/)


Most adapters that put a coding agent behind A2A flatten everything to text in, text out. a2acode keeps the structure the agent produces: the tools it runs, the files it changes, what it costs, the approvals it needs, and how to continue on the next turn. It bridges two Linux Foundation interop standards — **ACP** (how editors and clients talk to coding agents) on the agent side, **A2A** (how agents delegate to each other) on the caller side — so any ACP agent becomes a peer any A2A orchestrator can call.

How it maps to A2A

The coding agent produces	A2A surface it lands on
Assistant text	A streamed artifact (append / last_chunk)
Its reasoning	A separate thinking artifact, never the answer
A tool call (Bash, Edit)	A working status update for the action
That tool's outcome	A working status update: ✓ Bash / ✗ Bash: …
I