What problem does it solve?
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. 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.
Core Features & Use Cases
- Route requests to either the OpenClaw ACP runtime path or the direct acpx path based on intent and availability.
- Enforce preflight for coding-agent thread requests and use sessions_spawn with runtime acp, thread: true, mode: session for spawns, and specify agentId when needed.
- Maintain agentId mappings for common harness names (openclaw, claude, codex, copilot, cursor, droid, opencode, gemini, qwen, kilocode, kimi, kiro).
- Support mode selection and fallback options when ACP backend is unavailable, including direct acpx flows with appropriate defaults.
- Ensure not to use subagents runtime for ACP thread spawn and provide clear session-context management.
Quick Start
Describe the desired ACP harness workflow and specify whether to route to the OpenClaw ACP runtime or start a direct acpx session.