Connect Docker cagent to AgentRQ
Connect Docker cagent to AgentRQ over the Agent Client Protocol (ACP) for human-in-the-loop task management.
Docker cagent is Docker's containerized agent runtime, listed as ACP-compatible, so it can run behind AgentRQ's gateway with no custom integration code.
Does Docker cagent Support ACP?
Yes. Check cagent's repository for the exact command that starts it in ACP server mode.
What Connecting via ACP Gets You
Once cagent is bridged through AgentRQ's ACP Gateway, every task it works on shows up on your AgentRQ task board in real time. You can approve risky commands, reply with extra context, or reassign work — from the dashboard or Slack — without touching the terminal cagent is running in.
Connect Docker cagent
Once you have cagent's ACP command from its docs, wrap it with AgentRQ's gateway:
npx @agentrq/acp-gateway@latest -- <cagent-acp-command>
Then point it at your workspace with a .mcp.json in your project root:
{
"mcpServers": {
"agentrq": {
"type": "http",
"url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN"
}
}
}
See the ACP Gateway guide for the full setup walkthrough, including where to find your Workspace ID and token.
FAQ
Does Docker cagent work with AgentRQ?
Yes — cagent is listed as an ACP-compatible agent, so it connects to AgentRQ through the open-source ACP Gateway with no custom integration code.
How do I connect Docker cagent to AgentRQ?
Find cagent's ACP launch command in its official docs, then run npx @agentrq/acp-gateway@latest -- from your project root, with a .mcp.json pointing at your AgentRQ workspace.
What is the Agent Client Protocol (ACP)?
ACP is an open, editor-agnostic protocol that lets any coding agent talk to any client over a standard JSON-RPC interface. AgentRQ's gateway implements the client side of ACP, so any ACP-compatible agent — including Docker cagent — can use AgentRQ as its human-in-the-loop task manager.