acp-router

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

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Solitude01/proiect-new --skill acp-router-solitude01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/Solitude01/proiect-new/tree/main/%E5%88%9B%E6%84%8F/%E9%A3%9E%E7%89%9B/OPENCLAW/openclaw/openclaw/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/Solitude01/proiect-new --skill acp-router-solitude01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Route requests to ACP harness flows (runtime or direct acpx)
  • OpenClaw ACP runtime path: spawn ACP sessions with runtime acp, thread, and mode "session"; pass task; set agentId; avoid extra prompts
  • Direct acpx path: use exec to drive harness sessions; persistent or one-shot sessions; harness aliases; failure handling
  • Thread spawn recovery and ACPX install/version policy for reliability
  • AgentId mapping for standard harness agents (pi, claude, codex, opencode, gemini)

Quick Start

Tell OpenClaw to route a plain-language task to an ACP harness session or directly drive it via acpx.

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 an ACP harness session?

Routing plain-language requests to an ACP harness session involves directing tasks to either an OpenClaw ACP runtime path or a direct acpx-driven flow. The router handles session spawning, thread management, and agent mapping automatically.

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

The OpenClaw ACP runtime path spawns sessions with runtime acp, thread, and session mode execution. The direct acpx path uses exec to drive harness sessions, supporting persistent or one-shot flows when runtime access is unavailable.

How do I map agentId values for standard harness agents like Claude, Codex, or Gemini?

Mapping agentId values for standard harness agents involves configuring identifiers for agents like pi, claude, codex, opencode, and gemini. The router uses these mappings to correctly assign tasks within the ACP harness session lifecycle.

Does acpx routing support failure handling and thread spawn recovery?

Yes, acpx routing supports failure handling and thread spawn recovery. It includes ACPX install and version policies to ensure reliable routing and manage session lifecycle even when direct acpx-driven sessions encounter errors.

Can I use a direct acpx flow for persistent sessions when OpenClaw runtime access is unavailable?

Yes, you can use the direct acpx flow for persistent or one-shot sessions when OpenClaw runtime access is unavailable. This path uses exec to drive harness sessions and includes failure handling for reliability.