acp-router

Routes harness requests to OpenClaw ACP runtime or acpx sessions with preflight checks and agent mapping.

Updated Dec 6, 2016
One-click install
npx skills add https://github.com/majunbao/learn --skill acp-router-majunbao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/majunbao/learn/tree/main/openclaw_tags/openclaw-2026.3.2/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/majunbao/learn --skill acp-router-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language harness requests to either OpenClaw ACP runtime sessions or direct acpx-driven sessions.

Core Features & Use Cases

  • Route to ACP runtime or direct acpx path depending on availability
  • Enforce preflight checks for coding-agent thread requests
  • Map agent names to ACP IDs and manage session lifecycle
  • Provide safe, deterministic execution in either path

Quick Start

Route a harness task to the appropriate ACP harness path (OpenClaw ACP runtime or direct acpx) 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 the correct ACP runtime session?

Route harness tasks by evaluating availability and mapping agent names to ACP IDs, directing requests to either ACP runtime sessions or direct acpx-driven sessions for safe execution.

What is the difference between ACP runtime and direct acpx sessions for task routing?

ACP runtime sessions and direct acpx sessions are two execution paths for harness tasks; the router selects the appropriate path based on availability and preflight checks to ensure deterministic execution.

How do preflight checks work for coding-agent thread requests in ACP routing?

Preflight checks for coding-agent thread requests validate conditions before routing, ensuring safe, deterministic execution in either the ACP runtime or direct acpx-driven session path.

Can I map agent names to ACP IDs for session lifecycle management?

Map agent names to ACP IDs to manage the session lifecycle, enabling the router to correctly identify and direct harness tasks to the appropriate ACP runtime session.

What's the best way to ensure deterministic execution when routing ACP harness tasks?

Ensure deterministic execution by using the router to enforce preflight checks and map agent names to ACP IDs, routing tasks to either the ACP runtime or acpx path based on availability.

Why does my harness task routing fail when the ACP runtime is unavailable?

Harness task routing may fail if the ACP runtime is unavailable and preflight checks do not pass; the router depends on these checks to safely direct tasks to the correct session path.