Connect Codex
Use the open-source @agentrq/acp-gateway with the codex-acp agent to connect OpenAI Codex to AgentRQ.
Heads up: @agentrq/codex-gateway is retired. Codex now connects through @agentrq/acp-gateway and the codex-acp agent, which speaks the Agent Client Protocol (ACP) — the same gateway every other ACP agent uses.
The gateway runs codex-acp for you and bridges it to your
AgentRQ workspace, so Codex picks up tasks, asks for permission on risky commands, and reports
back — all from the dashboard or Slack.
1 Configure Your Workspace (.mcp.json)
Set up .mcp.json as usual — create it in your project root so the gateway knows which AgentRQ workspace to receive tasks from. You can copy it straight from Settings → Setup in the AgentRQ app.
{
"mcpServers": {
"agentrq": {
"type": "http",
"url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN"
}
}
}2 Log In to Codex
Run this once from the same directory. The first run also downloads the codex-acp agent, so there is nothing to install by hand.
npx @agentrq/acp-gateway@latest --login --agent codex-acp3 Spin Up the Gateway
Start the bridge from your workspace root (the directory containing .mcp.json). Leave it running — it picks up tasks as you assign them. --max-concurrency 1 keeps Codex working on one task at a time.
npx @agentrq/acp-gateway@latest --max-concurrency 1 --agent codex-acpNote: the gateway works the same way for every ACP agent — see the ACP Gateway guide for the full walkthrough, and the Codex CLI page for Codex-specific notes.
4 What the Gateway Bridges
Forwarded from AgentRQ to your agent as ACP prompts.
ACP agent requests permission → Gateway proxies to AgentRQ → verdict returned.
Agents can read and write files relative to the current directory.
Proxies ACP tool calls directly to AgentRQ MCP server tools.
Open Source Gateway
The ACP Gateway is open-source and community-driven. You can inspect the code, contribute fixes, or build your own specialized bridge.
View on GitHub