acp-router

Routes plain-language harness requests to OpenClaw ACP runtime or acpx sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language harness requests to either OpenClaw ACP runtime sessions or direct acpx-driven sessions, enabling robust harness orchestration and deterministic task routing.

Core Features & Use Cases

  • OpenClaw ACP runtime path for end-to-end harness lifecycle control, including thread creation and session management.
  • Direct acpx path for telephone-game style prompt relays when ACP is unavailable or explicitly requested.
  • Explicit agentId mapping and deterministic session handling with built-in recovery and fallback strategies to ensure reliability across diverse harness tasks.

Quick Start

Provide a harness task to be executed and the system will route it through the appropriate ACP runtime or acpx flow for execution.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I route harness tasks to ACP runtime sessions?

The acp-router routes harness tasks to either OpenClaw ACP runtime sessions or acpx-driven sessions, providing deterministic thread-spawn, explicit agentId mapping, and built-in recovery strategies to ensure reliable execution across diverse harness workflows.

When should I use acpx sessions instead of ACP runtime for harness routing?

Use acpx sessions for direct telephone-game style prompt relays when the OpenClaw ACP runtime is unavailable or explicitly requested, while ACP runtime sessions provide full harness lifecycle control, thread creation, and session management.

Does harness routing support automatic fallback and recovery?

Yes, harness routing supports automatic fallback and recovery through built-in strategies that coordinate ACP lifecycle and acpx flows, ensuring safe and reliable harness execution even when primary runtime sessions encounter failures.

How does deterministic thread-spawn work for ACP session routing?

Deterministic thread-spawn for ACP session routing works by using explicit agentId mapping and policy-driven behavior to coordinate thread creation, ensuring consistent and predictable harness task execution within the OpenClaw ACP runtime.

What is the best way to manage ACP lifecycle and acpx flows together?

The best way to manage ACP lifecycle and acpx flows together is through acp-router, which coordinates both paths using policy-driven behavior, explicit agentId mapping, and built-in recovery strategies to ensure safe and reliable harness execution.

Do I need explicit agentId mapping for plain-language harness requests?

Yes, explicit agentId mapping is supported for plain-language harness requests to ensure deterministic session handling, allowing the router to accurately map tasks across ACP runtime or acpx flows with built-in recovery and fallback strategies.