acp-router

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for ACP harness usage to the appropriate OpenClaw ACP runtime sessions or direct acpx-driven sessions.

Core Features & Use Cases

  • Route requests to either ACP runtime sessions or direct acpx flows based on user intent and task requirements.
  • Support OpenClaw ACP runtime path with session management and deterministic thread handling.
  • Offer a direct acpx path for telephone-game style harness control when runtime path is unavailable.

Quick Start

Route the user's harness request to the correct ACP session to begin execution immediately.

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 requests to the correct coding-agent session?

Route ACP harness requests by analyzing user intent to map agentId and select the appropriate OpenClaw ACP runtime session or direct acpx-driven session. The router enforces preflight checks and deterministic session naming to ensure safe thread-spawn execution.

What is the difference between the OpenClaw ACP runtime path and a direct acpx flow?

The OpenClaw ACP runtime path provides full session management with deterministic thread handling, while the direct acpx path offers telephone-game style harness control. The direct acpx flow serves as a fallback when the runtime path is unavailable.

How do I manage ACP session lifecycles for multiple coding-agent threads?

Manage ACP session lifecycles by using deterministic session naming and preflight checks before routing requests. This enforces safe runtime path selection and thread-spawn operations across multiple agent sessions.

Can I use acp-router to select a specific runtime path based on agent intent?

Yes, acp-router selects the runtime path by evaluating user intent and task requirements. It applies clear mode selection rules to map requests to either the OpenClaw ACP runtime or direct acpx sessions.

Why does my ACP thread-spawn fail during session initialization?

ACP thread-spawn failures during session initialization often occur when preflight checks fail or session naming rules are violated. Enforce deterministic session naming and clear mode selection to ensure safe session lifecycle management.