acp-router

Route ACP harness intents to OpenClaw runtime or acpx sessions.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill acp-router-arry8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/Arry8/openclaw-edge/tree/main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill acp-router-arry8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route user intents for ACP harness work to the appropriate OpenClaw ACP runtime sessions or direct acpx-driven sessions.

Core Features & Use Cases

  • Preflight checks for coding-agent thread requests and routing decisions
  • AgentId mapping and mode selection between OpenClaw ACP runtime path and direct acpx path
  • Safe, deterministic session orchestration for ACP harness tasks

Quick Start

Tell OpenClaw to route an ACP harness task to the ACP runtime for a session named "codex" and run a sample command.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I route ACP harness prompts to the correct runtime session?

Route ACP harness prompts by mapping the agentId and selecting between an OpenClaw ACP runtime path or a direct acpx-driven session to ensure correct thread spawn behavior.

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

OpenClaw ACP runtime sessions provide managed orchestration, while direct acpx sessions offer a direct execution path; the router performs path selection between these runtimes based on routing decisions.

How does agentId mapping work for ACP session routing?

AgentId mapping identifies the target coding-agent thread request and determines whether to route the ACP harness task to the OpenClaw ACP runtime path or the direct acpx path.

Do I need to run preflight checks before spawning ACP threads?

Yes, preflight checks are required for coding-agent thread requests to validate routing decisions and ensure safe, deterministic session lifecycle management before ACP thread spawn behavior executes.

Can I use this routing automation to manage session lifecycles for coding-agent tasks safely?

Yes, the routing automation ensures safe, deterministic session orchestration for ACP harness tasks by performing preflight checks and enforcing correct session lifecycle management across runtimes.

What are the limitations of routing ACP harness work between multiple runtimes?

Routing ACP harness work is limited to selecting between OpenClaw ACP runtime and direct acpx paths, requiring valid agentId mapping and preflight checks to maintain deterministic session orchestration.