acp-router

Name: acp-router
Availability: InStock
Author: pertain

Route user requests to the correct ACP harness backend via OpenClaw ACP runtime or acpx sessions.

1|Updated Apr 10, 2026

Search Tags:#sessions #harness #route #acp #agent-mapping #thread-spawn

Ready to run

npx skills add https://github.com/pertain99/openclaw-better --skill acp-router-pertain99

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/pertain99/openclaw-better/tree/main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/pertain99/openclaw-better --skill acp-router-pertain99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for multiple ACP harness backends into the correct runtime sessions or direct acpx-driven flows, eliminating manual handoffs and confusion.

Core Features & Use Cases

Route requests to the correct ACP harness for Pi, Claude Code, Codex, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or ACP harness workflows.
Preflight and mode-selection: read the skill first in the same turn, then choose between the OpenClaw ACP runtime path or the direct acpx path for harness control.
OpenClaw ACP runtime path: spawn ACP sessions with runtime "acp", route tasks via a structured "task" payload, and apply explicit agentId mappings.
Direct acpx path: drive harness prompts through acpx CLI when the runtime path is unavailable or a direct exchange is preferred (telephone-game style).
Robust error handling and fallbacks: detect ACP backend issues, retry after local repair, and offer graceful alternatives.

Quick Start

Route a coding task through the ACP harness using the OpenClaw ACP runtime path.

Frequently Asked Questions about acp-router

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

FAQPage Schema

How do I route prompts to different ACP harness backends?▼

Routing prompts to ACP harness backends is handled by enforcing preflight checks and deterministic agentId mapping, directing requests into the correct OpenClaw ACP workflow or direct acpx sessions based on explicit mode selection.

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

The OpenClaw ACP runtime path spawns ACP sessions using a structured task payload, whereas the direct acpx path drives harness prompts through the acpx CLI when the runtime path is unavailable or a direct exchange is preferred.

Can I use this to route tasks to Claude Code, Cursor, or Gemini CLI?▼

Yes, you can route tasks to Claude Code, Cursor, Gemini CLI, and other supported harnesses by mapping plain-language requests to their specific ACP workflows or direct acpx-driven flows.

How do I handle ACP backend issues when spawning runtime threads?▼

Handling ACP backend issues involves robust error handling that detects failures, retries after local repair, and offers graceful fallback alternatives to ensure seamless harness orchestration.

Do I need to manually select the mode before routing a request to an ACP workflow?▼

No, explicit mode selection occurs automatically after reading the skill in the same turn, choosing between the OpenClaw ACP runtime path and the direct acpx path for harness control.