---
title: "Poolside ACP Setup | AgentRQ Docs"
url: https://agentrq.com/docs/agents/poolside
description: "Poolside ACP setup: run Poolside 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

# Poolside ACP Setup

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

[Poolside](https://github.com/poolsideai/pool) is an AI coding assistant 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 Poolside to use websites too? [Connect Poolside to WebMCP](https://agentrq.com/docs/webmcp/poolside) shows how it can call a site's WebMCP tools in your own Chrome.

## Does Poolside Support ACP?

Yes. Poolside publishes an ACP server to the [ACP registry](https://github.com/agentclientprotocol/registry) as `poolside`, so AgentRQ's gateway can fetch and run it by name — there is nothing to install by hand.

## What Connecting via ACP Gets You

Once Poolside 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 Poolside is running in.

## Connect Poolside

Run both commands from your project root — the directory holding your `.mcp.json`.

Log in (the first run also downloads the agent):

bash

```bash
npx @agentrq/acp-gateway@latest --login --agent poolside
```

Start the bridge, and leave it running — it picks up tasks as you assign them:

bash

```bash
npx @agentrq/acp-gateway@latest --agent poolside
```

That `.mcp.json` is what tells the gateway which workspace to take tasks from:

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 Poolside work with AgentRQ?**

Yes — Poolside 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 Poolside to AgentRQ?**

Run `npx @agentrq/acp-gateway@latest --login --agent poolside` from your project root, then start the bridge with the same command minus `--login`. A `.mcp.json` there points the gateway 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 Poolside — 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)
- → [Poolside on GitHub](https://github.com/poolsideai/pool)
- → [Agent Client Protocol specification](https://agentclientprotocol.com)
- → [AgentRQ ACP Gateway guide](https://agentrq.com/docs/connect-acp-agent)
- → [Connect Poolside to WebMCP](https://agentrq.com/docs/webmcp/poolside)