acp-router

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

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/JiayueMeng128/OpenClaw2Androidtrying --skill acp-router-jiayuemeng128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/JiayueMeng128/OpenClaw2Androidtrying/tree/main/openclaw/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/JiayueMeng128/OpenClaw2Androidtrying --skill acp-router-jiayuemeng128

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of directing plain-language coding requests to various AI coding environments like Pi, Claude Code, Codex, OpenCode, Gemini CLI, or ACP harness work, ensuring they are handled by either OpenClaw ACP runtime sessions or direct acpx-driven sessions.

Core Features & Use Cases

  • Intelligent Routing: Automatically directs requests to the appropriate coding environment based on user intent.
  • ACP Runtime Integration: Leverages sessions_spawn for seamless creation of ACP runtime sessions and threads.
  • Direct acpx Control: Provides a fallback "telephone game" flow using acpx CLI for direct harness control when needed.
  • AgentId Mapping: Maps common harness names (e.g., "pi", "codex") to their corresponding agentIds.
  • Robust Error Handling: Includes policies for thread spawn recovery and ACPX installation/version management.

Quick Start

Use the acp-router skill to start a codex session in a thread and tell 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 plain-language coding requests to ACP harnesses like Pi or Claude Code?

To route coding requests to ACP harnesses, this Skill directs plain-language prompts to OpenClaw ACP runtime sessions via `sessions_spawn` or falls back to direct `acpx` CLI execution, mapping agent names like "pi" or "codex" to their corresponding agentIds.

What happens if the OpenClaw ACP runtime is unavailable when spawning a coding agent thread?

If the OpenClaw ACP runtime is unavailable, the routing mechanism implements recovery policies by falling back to a direct `acpx` CLI execution flow, ensuring coding tasks still proceed even without the primary ACP backend.

Can I use acpx directly to control coding agents like Codex or Gemini CLI?

Yes, you can use `acpx` directly to control coding agents like Codex or Gemini CLI. The router provides a fallback "telephone game" flow using the `acpx` CLI for direct harness control when the OpenClaw ACP runtime path is not used.

How does agentId mapping work for coding agents in an ACP session?

AgentId mapping translates common harness names such as "pi" and "codex" into their corresponding `agentId` values, allowing the router to correctly identify and dispatch tasks to the specified coding environment within the ACP session.

Do I need to install acpx separately to manage coding-agent thread creation?

You need `acpx` installed for direct harness control and fallback execution. The Skill includes policies for ACPX installation and version management to ensure the coding-agent thread creation and routing process functions correctly.

What is the best way to start a Codex session in an ACP thread?

The best way to start a Codex session is to route the request through the acp-router, which prioritizes the OpenClaw ACP runtime path via `sessions_spawn` to seamlessly create the thread and dispatch the task to the Codex agentId.