acp-router

Route plain-language harness requests to ACP runtimes or direct acpx execution.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/papachong/RHClaw --skill acp-router-papachong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/papachong/RHClaw/tree/main/RHClaw-Desktop/src-tauri/skills/acp-router
Command: npx skills add https://github.com/papachong/RHClaw --skill acp-router-papachong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect runtime choices and fragile interactions by routing plain-language harness requests for external coding agents into the correct ACP-aware execution path or a direct acpx-driven flow, avoiding subagents, PTY scraping, and improper thread creation.

Core Features & Use Cases

  • Intent detection: Recognizes requests to run work in Pi, Claude Code, Codex, OpenCode, Gemini, or Kimi and enforces ACP-aware handling.
  • Mode selection & mapping: Chooses between OpenClaw ACP runtime (sessions_spawn) and direct acpx CLI execution, and maps common harness names to agentId defaults.
  • Thread spawn and recovery: Requires reading this skill before thread creation, enforces sessions_spawn for threads, and includes automated install/repair and retry policies for ACP backends.
  • Safe acpx usage: Prefers plugin-local acpx binaries, verifies pinned versions, and provides explicit fallback and output-relay rules for telephone-game direct CLI flows.

Quick Start

Spawn a codex harness thread using the ACP runtime and instruct it to say hi.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I route coding agent harness requests to the correct ACP runtime?

Route coding agent harness requests by detecting intent and mapping plain-language requests to the correct OpenClaw ACP sessions_spawn runtime or direct acpx CLI execution path, preventing incorrect runtime choices and fragile PTY scraping.

What is the best way to manage thread creation for Claude Code and Codex in OpenClaw?

The best way to manage thread creation is enforcing ACP-aware sessions_spawn for thread creation, continuation, and relay workflows, which includes explicit agentId mapping for Pi, Claude Code, Codex, OpenCode, Gemini, and Kimi harnesses.

How does acpx execution handle fallback and recovery when a plugin-local binary fails?

Acpx execution handles fallback by preferring plugin-local binaries, verifying pinned versions, and applying automated install/repair and retry policies for ACP backends, providing explicit output-relay rules for direct CLI flows.

Does this routing approach support Gemini and Kimi coding agents?

Yes, this routing approach supports Gemini and Kimi coding agents alongside Pi, Claude Code, Codex, and OpenCode, enforcing ACP-aware handling and mapping common harness names to agentId defaults for each.

Why should I avoid subagents and PTY scraping for coding-agent thread workflows?

You should avoid subagents and PTY scraping because they cause fragile interactions and incorrect runtime choices, whereas using sessions_spawn-based thread creation with explicit agentId mapping ensures stable ACP-aware execution.