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."