acp-router

Route user intents to CrawClaw ACP or direct acpx harness sessions.

30|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/qianleigood/crawclaw --skill acp-router-qianleigood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/qianleigood/crawclaw/tree/main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/qianleigood/crawclaw --skill acp-router-qianleigood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests to the appropriate ACP harness sessions, enabling cross-harness task orchestration and reducing manual routing overhead.

Core Features & Use Cases

  • Intent detection and routing to the correct ACP runtime path (CrawClaw ACP or direct acpx) based on user request and context.
  • Thread-based session management for coding-agent tasks, with safe fallbacks and policy checks.
  • Use cases include starting ACP harness threads, routing prompts to specific agents (e.g., codex, Claude, or other ACP harnesses), and switching between runtime paths.

Quick Start

Route a sample coding task to the ACP harness for execution.

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

To route plain-language prompts to ACP harness sessions, the Skill detects user intent and directs requests to the appropriate ACP runtime path, such as the default CrawClaw ACP runtime via sessions_spawn.

Can I use a direct acpx path instead of the CrawClaw ACP runtime?

Yes, you can use a direct acpx path. While the default routing targets the CrawClaw ACP runtime via sessions_spawn, the Skill supports a direct acpx path as a fallback when explicitly requested by the user.

How does intent detection work for coding-agent thread management?

Intent detection for coding-agent thread management works by evaluating the user request and context to initiate thread-based sessions, applying safe fallbacks and policy checks to ensure correct ACP harness routing.

What is the best way to start a coding-agent thread across multiple ACP harnesses?

The best way to start a coding-agent thread across multiple ACP harnesses is to use this routing mechanism, which enables cross-harness task orchestration and reduces manual routing overhead for coding-agent tasks.

Does ACP routing support switching between different agents like codex or Claude?

Yes, ACP routing supports switching between different agents. Use cases include routing prompts to specific agents like codex, Claude, or other ACP harnesses, and switching between runtime paths based on context.

When should I not use the default CrawClaw ACP runtime for session routing?

You should not use the default CrawClaw ACP runtime when you explicitly need a direct acpx path fallback. The default runtime via sessions_spawn is bypassed only when an explicit direct acpx request is made.