Connect OpenHands to AgentRQ
Connect OpenHands to AgentRQ over the Agent Client Protocol (ACP) for human-in-the-loop task management.
OpenHands (formerly OpenDevin) is an open-source autonomous software engineering agent. It supports the Agent Client Protocol (ACP), so it can run behind AgentRQ's gateway with no custom integration code.
Does OpenHands Support ACP?
Yes. The openhands acp command starts OpenHands as an ACP server, enabling communication with any ACP client over JSON-RPC via stdio.
What Connecting via ACP Gets You
Once OpenHands 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 OpenHands is running in.
Connect OpenHands
Wrap OpenHands's ACP mode with AgentRQ's gateway:
npx @agentrq/acp-gateway@latest -- openhands 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 OpenHands work with AgentRQ?
Yes — OpenHands 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 OpenHands to AgentRQ?
Run npx @agentrq/acp-gateway@latest -- openhands 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 OpenHands — can use AgentRQ as its human-in-the-loop task manager.