acp-router

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RJB07/RX01 --skill acp-router-rjb07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/RJB07/RX01/tree/main/core/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/RJB07/RX01 --skill acp-router-rjb07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for ACP harnesses into either RX01 ACP runtime sessions or direct acpx-driven sessions.

Core Features & Use Cases

  • Route requests to RX01 ACP runtime sessions or direct acpx flows based on user intent, supporting Pi, Claude Code, Codex, OpenCode, Gemini, and Kimi harnesses.
  • Enforce preflight checks for coding-agent thread requests and ensure thread-spawn uses the correct ACP path.
  • Map harness names to internal agent IDs and provide clear guidance when policy blocks a choice.

Quick Start

Spawn a codex ACP thread via the router and have it respond with a greeting.

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 ACP harness sessions?

Route ACP harness requests by evaluating user intent to direct plain-language inputs into either RX01 ACP runtime sessions or direct acpx-driven sessions, selecting the appropriate execution path automatically.

Does the ACP router support Claude Code, Codex, and Gemini harnesses?

Yes, the ACP router supports coding-agent thread requests and harness management across Pi, Claude Code, Codex, OpenCode, Gemini, and Kimi by mapping harness names to internal agent IDs.

What is the difference between RX01 ACP runtime sessions and direct acpx sessions?

RX01 ACP runtime sessions use the sessions_spawn path, which the router favors when appropriate, while direct acpx-driven sessions provide an alternative flow based on specific request preflight checks.

How do I spawn a coding-agent thread using ACP routing?

Spawn an ACP thread by submitting a request to the router, which enforces ACP-specific thread spawn rules and performs preflight checks, favoring the ACP runtime path via sessions_spawn when conditions are met.

Why does policy block my ACP harness routing choice?

Policy blocks an ACP harness choice when preflight checks fail or the request violates ACP-specific thread spawn rules, with the router providing clear guidance explaining why the selected path was rejected.