Connect Bub to AgentRQ
Connect Bub to AgentRQ over the Agent Client Protocol (ACP) for human-in-the-loop task management.
Bub is a build system that ships its own ACP server (bub-acp-server), so it can run behind AgentRQ's gateway with no custom integration code.
Does Bub Support ACP?
Yes, via bub-acp-server. Check Bub's repository for the exact command that starts it in ACP server mode.
What Connecting via ACP Gets You
Once Bub 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 Bub is running in.
Connect Bub
Once you have Bub's ACP command from its docs, wrap it with AgentRQ's gateway:
npx @agentrq/acp-gateway@latest -- bub-acp-server
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 Bub work with AgentRQ?
Yes — Bub ships an ACP server (bub-acp-server), so it connects to AgentRQ through the open-source ACP Gateway with no custom integration code.
How do I connect Bub to AgentRQ?
Run npx @agentrq/acp-gateway@latest -- bub-acp-server from your project root (check Bub's docs for any required flags), 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 Bub — can use AgentRQ as its human-in-the-loop task manager.