What problem does it solve? When you ask an agent to run work in external coding harnesses like Pi, Claude Code, Codex, OpenCode, Gemini, or Kimi, it is easy to pick the wrong execution path (subagent runtimes, PTY scraping, or manual CLI relay). This Skill standardizes that routing so harness requests go through the correct ACP-aware flow every time. ## Core Features & Use Cases - Intent-based routing: Detects requests to run or continue work in Pi, Claude Code, Codex, OpenCode, Gemini, or Kimi and maps them to the correct ACP agentId. - Dual execution paths: Chooses between the OpenClaw ACP runtime path (sessions_spawn with runtime acp) and the direct acpx telephone-game path for relaying prompts to harness sessions. - Session lifecycle management: Provides deterministic session naming, command templates for creating, prompting, canceling, and closing acpx sessions, plus pinned-version install and recovery policies. - Use Case: A user says "start a Codex thread and have it review this repo." The Skill reads the routing rules, spawns an ACP thread session via sessions_spawn, and falls back to direct acpx commands with automatic repair if the ACP backend is unavailable. ## Quick Start Ask the agent to start a Codex (or Claude Code, Pi, Gemini) thread and give it a task, and it will route the request through the ACP runtime automatically.