What problem does it solve? When you ask an assistant to run work in an external coding harness like Claude Code, Cursor, Copilot, Gemini CLI, or Codex, it is easy to pick the wrong execution path (subagent runtimes, PTY scraping, or manual slash commands). This Skill standardizes that routing so harness requests reliably go through ACP-aware sessions with correct agent IDs, thread handling, and recovery. ## Core Features & Use Cases - Intent-based routing: Detects requests for Claude Code, Cursor, Copilot, OpenCode, Gemini, Qwen, Kiro, Kimi, iFlow, Droid, Kilocode, OpenClaw, and Codex, then maps them to the correct ACP agentId. - Two execution paths: Uses the OpenClaw ACP runtime via sessions_spawn by default, or a direct acpx CLI telephone-game flow when the runtime is unavailable or explicitly requested. - Self-repair and recovery: 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 reads its routing rules, calls sessions_spawn with runtime acp, agentId codex, and thread mode, then relays the harness response back. ## Quick Start Ask the assistant to run a task in your preferred coding harness, for example: "Run this refactor in Claude Code in a thread and report back what it changed."