acp-router

Routes automation requests to appropriate WebSocket or CLI targets based on intent and payload.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language harness requests to the correct ACP flow, enabling OpenClaw to manage sessions either via the built-in ACP runtime or via direct acpx paths.

Core Features & Use Cases

  • Route user intent to ACP harness flows (runtime) or direct acpx paths
  • Map agentIds and select the appropriate path based on user request and system state
  • Ensure preflight checks for coding-agent thread requests and consistent payloads

Quick Start

Route a request to start a Pi session and let ACP-router choose the proper path.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I route plain-language requests to ACP harness sessions?

ACP routing maps plain-language requests to the correct flow by applying intent detection, preflight threading checks, and agentId mapping to select either a runtime session via sessions_spawn or a direct acpx path via exec.

What is the difference between runtime sessions and direct acpx paths in ACP?

Runtime sessions use sessions_spawn with runtime ACP and thread true, whereas direct acpx paths execute via exec to manage sessions directly through the acpx interface without the built-in runtime.

Does ACP routing support coding agents like Claude Code, Cursor, and Copilot?

ACP routing supports agentId mapping across Pi, Claude Code, Codex, Cursor, and Copilot, ensuring consistent task payloads are routed to the correct harness target for each coding agent.

When do I need preflight checks for ACP thread requests?

Preflight checks for ACP thread requests are needed when routing coding-agent intents to verify the system state can support threading before spawning runtime sessions or executing direct acpx paths.

How to map agentIds for ACP harness targets across different coding agents?

To map agentIds for ACP harness targets, the router evaluates the user request and system state to provide a consistent task payload and agentId for targets including Pi, Claude Code, Codex, Cursor, and Copilot.

Why does my ACP harness request fail to route to the correct session?

ACP harness requests fail to route correctly when intent detection cannot distinguish between runtime and direct acpx paths, or when preflight threading checks and agentId mapping encounter inconsistent task payloads.