acp-router

Route coding-harness requests to ACP runtime or acpx-backed sessions.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill acp-router-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill acp-router-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions. For coding-agent thread requests, read this skill first, then use only sessions_spawn for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.

Core Features & Use Cases

  • Route requests to either the OpenClaw ACP runtime path or the direct acpx path based on intent and availability.
  • Enforce preflight for coding-agent thread requests and use sessions_spawn with runtime acp, thread: true, mode: session for spawns, and specify agentId when needed.
  • Maintain agentId mappings for common harness names (openclaw, claude, codex, copilot, cursor, droid, opencode, gemini, qwen, kilocode, kimi, kiro).
  • Support mode selection and fallback options when ACP backend is unavailable, including direct acpx flows with appropriate defaults.
  • Ensure not to use subagents runtime for ACP thread spawn and provide clear session-context management.

Quick Start

Describe the desired ACP harness workflow and specify whether to route to the OpenClaw ACP runtime or start a direct acpx session.

Frequently Asked Questions about acp-router

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

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

Route ACP tasks by evaluating request intent and backend availability to select either the OpenClaw ACP runtime path or a direct acpx-driven session. This ensures thread-spawn requests hit the correct runtime with proper preflight validation.

Can I use subagents runtime for ACP thread spawn?

No, you cannot use the subagents runtime for ACP thread spawn. You must use sessions_spawn with runtime acp, thread: true, and mode: session to ensure proper thread creation and session-context management.

How do I manage agent mappings for coding harnesses like Claude, Cursor, and Copilot?

Manage agent mappings by specifying the agentId parameter during session spawn. Supported mappings include openclaw, claude, codex, copilot, cursor, droid, opencode, gemini, qwen, kilocode, kimi, and kiro.

What happens if the ACP backend is unavailable during a thread spawn?

If the ACP backend is unavailable, the routing logic supports fallback options including direct acpx flows with appropriate defaults. Mode selection and fallback logic ensure requests complete even without the primary ACP runtime.

Does Codex chat binding default to the ACP runtime or native app-server?

Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicitly requested or background spawn needs ACP. This prevents unnecessary ACP routing for standard Codex interactions.

When do I need preflight checks for coding-agent thread requests?

Preflight checks are required for all coding-agent thread requests before creation. They validate runtime path selection, thread creation rules, and agent mappings to ensure sessions_spawn executes correctly across multiple agent types.