Connect Augment Code to AgentRQ
Connect Augment Code (Auggie) to AgentRQ over the Agent Client Protocol (ACP) for human-in-the-loop task management.
Augment Code is an AI coding assistant built for large, real-world codebases, with a CLI ("Auggie") that supports the Agent Client Protocol (ACP).
Does Augment Code Support ACP?
Yes. Passing the --acp flag to Auggie starts it as an ACP server, ready for any ACP client — including AgentRQ's gateway — to connect over stdio.
What Connecting via ACP Gets You
Once Auggie 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 Auggie is running in.
Connect Augment Code
Wrap Auggie's ACP mode with AgentRQ's gateway:
npx @agentrq/acp-gateway@latest -- auggie --acp
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 Augment Code work with AgentRQ?
Yes — Augment Code's Auggie CLI speaks the Agent Client Protocol (ACP), so it connects to AgentRQ through the open-source ACP Gateway with no custom integration code.
How do I connect Augment Code to AgentRQ?
Run npx @agentrq/acp-gateway@latest -- auggie --acp 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 Augment Code — can use AgentRQ as its human-in-the-loop task manager.