CLI coding agents over ACP

Drive external CLI coding agents — Claude Code, Codex, OpenCode — as first-class AG2 Agents, using the Agent Client Protocol (ACP). AG2 plays the ACP Client role; each CLI agent runs as an ACP Agent subprocess. Everything the agent does — message output, thinking, tool calls, plans, permission prompts — is externalized onto AG2's event stream, so you can observe, gate, and orchestrate it like any other AG2 agent.

The integration is just a config class (ACPConfig and its presets) — no changes to the Agent API.

When to use

• You want to orchestrate CLI coding agents from Python: headless refactoring pipelines, "manager" agents delegating to coder agents, batch code-mod runs.
• You want to observe a coding agent's work live — thoughts, tool calls, plans — on the AG2 event stream.
• You want to gate the agent's sensitive actions (file writes, shell commands) with a permission policy or a human in the loop.
• You need the agent's file access confined to a workspace root (fs_root) and its terminal use mediated by AG2.

Not this skill: exposing an AG2 agent to other systems — that is ag2-a2a (A2A protocol) or ag2-mcp (MCP server). For the HITL input plumbing that permission_policy="ask" relies on, see ag2-hitl.

Installation