Agent skill · software engineering · steipete
acp-router
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.
Why this skill is useful
Adds executable routing logic and session management scripts for various ACP harnesses that aren't publicly documented.
What it needs
Requires openclaw installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
ACP Harness Router When user intent is "run this in Claude Code/Cursor/Copilot/OpenClaw/OpenCode/Gemini/Qwen/Kiro/Kimi/iFlow/Droid/Kilocode (ACP harness)", do not use subagent runtime or PTY scraping. Route through ACP-aware flows. Codex is special: plain chat/conversation binding and control should use the native Codex app-server plugin (/codex bind, /codex threads, /codex resume) instead of the default ACP path. Use ACP for Codex only when the user explicitly names ACP//acp/acpx, or when spawning background child sessions through sessionsspawn where a native Codex runtime spawn is not available yet. Intent detection Trigger this skill when the user asks OpenClaw to: run something in Claude Code / Cursor / Copilot / OpenClaw / OpenCode / Gemini / Qwen / Kiro / Kimi / iFlow / Droid / Kilocode run Codex explicitly through ACP, /acp, or acpx continue existing harness work relay instructions to an external coding harness keep an external harness conversation in a thread-like conversation Mandatory preflight for coding-agent thread requests: Before creating any thread for ACP harness work, read this skill first in the same turn. After reading, follow OpenClaw ACP runtime path below; do not use message(action="thread-create") for ACP harness thread spawn. Mode selection Choose one of these paths: 1. OpenClaw ACP runtime path (default): use sessionsspawn / ACP runtime tools. 2. Direct acpx path (telephone game): use acpx CLI through exec to drive the harness session directly. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/acp-router