acp-router

Route coding harness requests to ACP runtime sessions or acpx flows.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill acp-router-johnnywhitemike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/JOHNNYWHITEMIKE/openclaw/tree/main/openclaw/.openclaw/openclaw/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill acp-router-johnnywhitemike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or inefficient “telephone game” routing when users ask OpenClaw to run work inside various ACP-compatible coding harnesses.

Core Features & Use Cases

  • Intent-based harness routing: Detects when the user requests Pi, Claude Code, Codex, Cursor, Copilot, OpenClaw ACP/OpenCode, Gemini/Qwen/Kiro/Kimi, iFlow, Factory Droid, Kilocode, or an ACP harness.
  • Two execution modes with guardrails: Routes either through OpenClaw ACP runtime using sessions_spawn (preferred when available) or through a direct acpx “telephone game” exec path when explicitly requested or when the ACP runtime/plugin path is unavailable.
  • Thread spawn correctness: Enforces that ACP harness thread creation uses sessions_spawn (no message action=thread-create) and requires skill re-reading before thread creation for coding-agent requests.

Quick Start

Ask: “Route my request to run the following in Claude Code harness and keep it in a thread: [your prompt].”

Frequently Asked Questions about acp-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route coding harness requests to specific ACP agents like Claude Code or Cursor?

ACP routing detects plain-language requests for coding harnesses like Claude Code or Cursor and maps the intent to the correct agentId. It then directs the request through the OpenClaw ACP runtime using sessions_spawn for proper execution.

What is the difference between sessions_spawn routing and the acpx telephone-game flow?

The sessions_spawn route executes work through the OpenClaw ACP runtime, while the acpx telephone-game flow is a direct execution path. ACP runtime routing is preferred when available, with acpx used as an explicit request or fallback when the runtime is unhealthy.

Does ACP harness routing support thread creation for continuing existing coding conversations?

Yes, ACP harness routing supports continuing existing conversations by enforcing thread spawn correctness. It requires thread creation via sessions_spawn rather than message actions, and mandates skill re-reading before spawning threads for coding-agent requests.

Can I use ACP routing with multiple coding agents like Pi, Codex, Copilot, and Gemini?

ACP routing supports intent detection and agentId mapping for numerous coding agents including Pi, Codex, Copilot, Gemini, Qwen, Kiro, Kimi, iFlow, Factory Droid, and Kilocode, routing requests to the appropriate target.

What happens when the ACP backend or plugin-local acpx is unhealthy during harness routing?

When the ACP backend or plugin-local acpx is unhealthy, the routing mechanism applies a defined fallback behavior. It redirects the harness request to the direct acpx telephone-game execution path to ensure the coding task still processes.