acp-router

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill decides whether a plain-language request to run code or interact with an external coding harness should be handled by Kova's ACP runtime or driven directly via the acpx CLI, preventing incorrect thread creation methods and unsafe PTY scraping.

Core Features & Use Cases

  • Intent detection and mapping: Recognizes requests mentioning Pi, Claude Code, Codex, Cursor, Copilot, Kova ACP, OpenCode, Gemini, Qwen, Kiro, Kimi, iFlow, Droid, Kilocode and maps them to default agentId values.
  • ACP runtime orchestration: Enforces sessions_spawn with runtime set to acp, thread=true, and mode=session while placing requested work in the task payload for immediate execution.
  • Direct acpx telephone-game flow: Provides templates and policies for invoking a plugin-local acpx binary, deterministic session naming, one-shot and persistent session patterns, and clean output relay.
  • Resilient recovery and safety rules: Includes install/repair steps for pinned acpx, restart and retry policies, adapter fallback guidance, and explicit failure handling for missing binaries and busy queues.

Quick Start

Ask Kova to spawn a codex ACP thread and instruct it to run the test suite so the assistant routes the request using the ACP runtime with sessions_spawn.

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 into ACP agent sessions?

Routing plain-language requests into ACP agent sessions involves mapping intent to default agentId values and enforcing sessions_spawn with the runtime set to acp, placing the requested task in the payload for immediate thread execution.

What is the difference between ACP runtime orchestration and direct acpx telephone-game flows?

ACP runtime orchestration enforces sessions_spawn for managed thread creation, while direct acpx telephone-game flows invoke a plugin-local acpx binary for one-shot or persistent sessions with deterministic naming and output relay policies.

Can I use this to route harness prompts for coding agents like Claude Code, Cursor, and Copilot?

Yes, this skill recognizes requests for Claude Code, Cursor, Copilot, Pi, Codex, Gemini, Qwen, Kiro, Kimi, iFlow, Droid, and Kilocode, mapping them to default agentId values for proper ACP session routing.

How do I handle a missing acpx binary or busy queue during direct session calls?

Handling a missing acpx binary or busy queue involves utilizing the skill's explicit failure handling, install and repair steps for pinned acpx, restart and retry policies, and adapter fallback guidance for resilient recovery.

Why should I use sessions_spawn instead of PTY scraping for ACP thread creation?

Using sessions_spawn instead of PTY scraping prevents incorrect thread creation methods and unsafe PTY scraping by enforcing structured thread creation with runtime, thread, and mode parameters set correctly for the ACP environment.