acp-router

Route ACP harness requests to runtime sessions or direct acpx flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for multiple ACP harness agents and ensure they are executed in the correct runtime path (UAGENT ACP runtime sessions or direct acpx-driven sessions).

Core Features & Use Cases

  • Intent-driven routing: automatically decide between ACP runtime path and direct acpx path based on user intent and policy.
  • AgentId mapping and mode selection: maps common harness names to agent IDs and selects the appropriate mode (runtime sessions vs acpx CLI).
  • Preflight and thread-management: enforces preflight checks before creating threads and handles thread spawn and recovery policies.
  • ACPX governance: provides install/version rules for direct acpx usage and restarts when artifacts are repaired.
  • Built-in templates: includes command templates and fallbacks for common harness scenarios.

Quick Start

Spawn an ACP harness session for a target agent and direct prompts through the appropriate ACP path as described.

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 harness requests to the correct runtime path?

ACP harness routing decides between ACP runtime sessions and direct acpx flows based on intent and policy. It evaluates user prompts, maps agent IDs, and selects the correct path to ensure execution in the appropriate runtime environment.

What is the difference between ACP runtime sessions and direct acpx flows?

ACP runtime sessions use UAGENT paths for managed execution, while direct acpx flows handle CLI-driven sessions. The router maps harness names to agent IDs and selects the mode based on policy to direct requests to the correct path.

How do I manage threads and preflight checks for ACP harness sessions?

Managing ACP threads requires enforcing preflight checks before spawning any new threads. The router handles thread spawn and recovery policies, ensuring the runtime environment passes all checks before creating a new session.

Can I use direct acpx flows without enforcing ACPX installation governance?

Direct acpx flows require ACPX installation and version governance. The router enforces these rules and provides fallback options, including restarting when artifacts are repaired, if the backend is unavailable or version checks fail.

What fallback options exist when the ACP backend is unavailable?

When the ACP backend is unavailable, the router provides built-in command templates and fallback options for common harness scenarios. It also restarts direct acpx flows once repaired artifacts are detected and governance checks pass.

Why does my ACP harness agent-id mapping fail to select the right mode?

Agent-id mapping fails when common harness names are not correctly mapped to agent IDs or when preflight checks are not met. The router uses intent-driven mapping to select between runtime sessions and acpx CLI modes to prevent this.