acp-router

Routes coding-agent requests to ACP runtime sessions or direct acpx CLI sessions.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/Tau_agent --skill acp-router-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/shalevamin/Tau_agent/tree/main/tau-agent-main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/shalevamin/Tau_agent --skill acp-router-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires acpx.

What problem does it solve? When you ask an agent to run work in external coding harnesses like Pi, Claude Code, Codex, OpenCode, Gemini, or Kimi, it is easy to pick the wrong execution path (subagent runtimes, PTY scraping, or manual CLI relay). This Skill standardizes that routing so harness requests go through the correct ACP-aware flow every time. ## Core Features & Use Cases - Intent-based routing: Detects requests to run or continue work in Pi, Claude Code, Codex, OpenCode, Gemini, or Kimi and maps them to the correct ACP agentId. - Dual execution paths: Chooses between the OpenClaw ACP runtime path (sessions_spawn with runtime acp) and the direct acpx telephone-game path for relaying prompts to harness sessions. - Session lifecycle management: Provides deterministic session naming, command templates for creating, prompting, canceling, and closing acpx sessions, plus pinned-version install and recovery policies. - Use Case: A user says "start a Codex thread and have it review this repo." The Skill reads the routing rules, spawns an ACP thread session via sessions_spawn, and falls back to direct acpx commands with automatic repair if the ACP backend is unavailable. ## Quick Start Ask the agent to start a Codex (or Claude Code, Pi, Gemini) thread and give it a task, and it will route the request through the ACP runtime automatically.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I run a task in Claude Code or Codex from my agent?

Phrase the request naturally, such as asking to start a Codex thread with a task. The router maps the harness name to an ACP agentId and spawns an ACP runtime session via sessions_spawn, or falls back to direct acpx CLI sessions when needed.

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

The ACP runtime path uses sessions_spawn with runtime acp and is the default for thread-based harness work. The direct acpx path drives harness sessions through the acpx CLI in a telephone-game flow, used when the runtime is unavailable or the user explicitly requests it.

Which coding agents does ACP routing support?

Supported harnesses are Pi, Claude Code, Codex, OpenCode, Gemini CLI, and Kimi. Each maps to a built-in acpx alias such as pi, claude, codex, opencode, gemini, or kimi, with default adapter commands like npx @zed-industries/codex-acp.

Why does ACP thread spawn fail and how is it recovered?

Failures usually come from a missing or mismatched acpx binary or broken adapter overrides in ~/.acpx/config.json. The recovery policy installs the pinned plugin-local acpx in extensions/acpx, restarts the gateway, and retries once before offering fallback options.

Should I use subagents or PTY scraping to control coding CLIs?

No. The routing rules explicitly prohibit subagent runtimes and PTY scraping of pi, claude, codex, opencode, gemini, or kimi CLIs when acpx is available. ACP-aware flows provide proper session lifecycle and thread semantics instead.