← Back to overview
Feature · Multi-Agent Coordination

Agent Cross-Project Coordination (ACP)

Real work often spans several projects — a backend and the library it consumes, for instance. IDEAgent uses the Agent Coordination Protocol (ACP) so one agent can ask the agent working on another project to make a change, then continue once it reports back.

See ACP in Action

This video demonstrates how IDEAgent handles cross-project coordination. Watch as one agent delegates tasks to a peer agent working in a different project repository, and how they report back when the work is complete.

Watch on YouTube: IDEAgent Cross Projects ACP ↗

How ACP Works

  • Turn-based, not blocking. acp_request delivers a masked request that starts a fresh, independent turn on the peer agent; the requesting agent's turn simply ends.
  • Report on completion. The peer's acp_report is delivered as a new turn on the original agent, which then resumes and finishes the task.
  • Cache-until-idle. If the target is busy or offline, the request/report waits and is redelivered when it next goes idle or reconnects — even across machines.

This design deliberately avoids graph-level suspension, so no node is ever replayed and each side runs one clean turn.