---
title: "stdio Bus ACP Setup | AgentRQ Docs"
url: https://agentrq.com/docs/agents/stdio-bus
description: "stdio Bus ACP setup: run stdio Bus over the Agent Client Protocol and connect it to AgentRQ for human-in-the-loop task management."
---

[Docs](https://agentrq.com/docs/) / Agents / Integrations

Integrations

# stdio Bus ACP Setup

stdio Bus ACP setup: run stdio Bus over the Agent Client Protocol and connect it to AgentRQ for human-in-the-loop task management.

[stdio Bus](https://github.com/stdiobus/stdiobus) is a stdio-based agent communication framework listed as ACP-compatible, so it can run behind AgentRQ's gateway with no custom integration code.

Wondering which other coding agents support ACP? See the [ACP support table](https://agentrq.com/blog/which-coding-agents-support-acp-agent-client-protocol) for 33 agents.

Want stdio Bus to use websites too? [Connect stdio Bus to WebMCP](https://agentrq.com/docs/webmcp/stdio-bus) shows how it can call a site's WebMCP tools in your own Chrome.

## Does stdio Bus Support ACP?

Yes. Check stdio Bus's [repository](https://github.com/stdiobus/stdiobus) for the exact command that starts it in ACP server mode.

## What Connecting via ACP Gets You

Once stdio Bus is bridged through AgentRQ's [ACP Gateway](https://agentrq.com/docs/connect-acp-agent), every task it works on shows up on your AgentRQ [task board](https://agentrq.com/features/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 stdio Bus is running in.

## Connect stdio Bus

Once you have stdio Bus's ACP command from its docs, wrap it with AgentRQ's gateway:

bash

```bash
npx @agentrq/acp-gateway@latest -- <stdio-bus-acp-command>
```

Then point it at your workspace with a `.mcp.json` in your project root:

json

```json
{
  "mcpServers": {
    "agentrq": {
      "type": "http",
      "url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN"
    }
  }
}
```

See the [ACP Gateway guide](https://agentrq.com/docs/connect-acp-agent) for the full setup walkthrough, including where to find your Workspace ID and token.

## FAQ

**Does stdio Bus work with AgentRQ?**

Yes — stdio Bus is listed as an ACP-compatible agent, so it connects to AgentRQ through the open-source [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) with no custom integration code.

**How do I connect stdio Bus to AgentRQ?**

Find stdio Bus's ACP launch command in its [official docs](https://github.com/stdiobus/stdiobus), then run `npx @agentrq/acp-gateway@latest -- <that-command>` 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 stdio Bus — can use AgentRQ as its human-in-the-loop task manager.

## References

- → [Which coding agents support ACP?](https://agentrq.com/blog/which-coding-agents-support-acp-agent-client-protocol)
- → [stdio Bus on GitHub](https://github.com/stdiobus/stdiobus)
- → [Agent Client Protocol specification](https://agentclientprotocol.com)
- → [AgentRQ ACP Gateway guide](https://agentrq.com/docs/connect-acp-agent)
- → [Connect stdio Bus to WebMCP](https://agentrq.com/docs/webmcp/stdio-bus)