What problem does it solve? It removes the guesswork of deciding how to run work in external coding harnesses like Pi, Claude Code, Codex, OpenCode, or Gemini CLI by automatically routing requests to the correct ACP runtime session or direct acpx CLI flow. ## Core Features & Use Cases - Intent Detection and Routing: Recognizes when a user wants work run in an external coding harness and selects between the ErnOS ACP runtime path and the direct acpx telephone-game path. - Agent ID Mapping: Maps natural harness names like "claude" or "codex" to the correct ACP agentId aliases used by acpx. - Session Management and Recovery: Maintains persistent named sessions per conversation, handles NO_SESSION and queue-busy errors, and performs automatic repair of the pinned plugin-local acpx binary before falling back. - Use Case: A user says "start a codex thread and tell it to refactor the auth module" and the skill spawns an ACP thread session with the correct agentId, or drives acpx directly if the runtime is unavailable. ## Quick Start Ask ErnOS to spawn a Codex session in a thread and tell it to say hi.