acp-router

Routes coding-agent requests to ACP runtime sessions or direct acpx CLI sessions.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill acp-router-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill acp-router-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires acpx.

What problem does it solve? When you ask an assistant to run work in an external coding harness like Claude Code, Cursor, Copilot, Codex, or Gemini CLI, it is easy to pick the wrong execution path (subagent runtimes, PTY scraping, or manual slash commands). This Skill standardizes how those plain-language requests are routed into proper ACP (Agent Client Protocol) sessions so harness work runs in the right runtime with the right agent identity. ## Core Features & Use Cases - Intent-based routing: Detects requests to run work in Claude Code, Cursor, Copilot, OpenCode, Gemini, Qwen, Kiro, Kimi, iFlow, Droid, Kilocode, or Codex and maps them to the correct ACP agentId. - Two execution paths: Uses the OpenClaw ACP runtime via sessions_spawn by default, or falls back to direct acpx CLI sessions (the "telephone game" flow) when the runtime is unavailable. - Recovery and repair policy: Automatically reinstalls the pinned plugin-local acpx binary, restarts the gateway, and retries failed ACP thread spawns before offering fallbacks. - Use Case: A user says "spawn a Codex ACP session in a thread and tell it to say hi" — the Skill routes this to sessions_spawn with runtime acp, agentId codex, and thread mode, without asking the user to run any CLI commands. ## Quick Start Ask the assistant to run a task in your preferred coding harness, for example: "Run this refactor in Claude Code in a new thread."

Frequently Asked Questions about acp-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a task in Claude Code or Cursor from my assistant?

State the harness name in your request, such as "run this in Claude Code". The request is routed to an ACP session with the matching agentId (claude, cursor, etc.) using sessions_spawn, without requiring slash commands or manual CLI usage.

What is the difference between the ACP runtime path and direct acpx sessions?

The ACP runtime path uses sessions_spawn with runtime acp and is the default for thread-based harness work. The direct acpx path drives the harness CLI through exec commands and is used when the runtime is unavailable or the user explicitly requests direct acpx driving.

Which coding agents are supported through ACP and acpx?

Supported harnesses include Claude Code, Codex, Copilot, Cursor, Factory Droid, Gemini CLI, iFlow, Kilocode, Kimi, Kiro, OpenClaw, OpenCode, and Qwen. Each maps to a built-in acpx alias and adapter command, which can be overridden in ~/.acpx/config.json.

Does Codex use ACP by default for chat sessions?

No. Plain Codex chat binding uses the native Codex app-server plugin with commands like /codex bind and /codex threads. ACP is used for Codex only when explicitly requested or when spawning background sessions through sessions_spawn.

What happens when the ACP backend or acpx command is not available?

The flow first attempts automatic repair: installing the pinned plugin-local acpx binary, verifying its version, restarting the gateway, and retrying the spawn once. Only if repair fails does it report the error and offer fallback options.

When should I not use the ACP router for harness work?

Avoid it when the task does not involve an external coding harness, or when a native plugin path exists, such as Codex chat binding. It also prohibits subagent runtimes and PTY scraping of supported harness CLIs when acpx is available.