acp-router

Name: acp-router
Availability: InStock
Author: XAIHT

Route plain-language requests to ACPX harnesses and manage sessions via acp_spawn.

14|1|Updated Mar 6, 2026

Search Tags:#multi-agent #orchestration #session-management #harness #route #agent-routing #acp_spawn

Ready to run

npx skills add https://github.com/XAIHT/Tlamatini --skill acp-router-xaiht

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/acp_router
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill acp-router-xaiht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests to ACPX child sessions and orchestrate task routing across multiple heterogeneous agents via acp_spawn, acp_send, and management primitives.

Core Features & Use Cases

Intelligent harness routing: map user intent to the appropriate ACPX harness (claude, cursor, codex, copilot, gemini, qwen, pi, droid, iflow, kilocode, kimi, kiro, opencode, tlamatini) and return a session.
Session lifecycle management: coordinate acp_spawn, acp_send, and acp_kill to maintain deterministic sessions or one-shot interactions.
Multi-agent orchestration: enable cross-agent tasks and safe transport awareness with agentId selection and error handling.

Quick Start

Spawn an ACPX session by selecting a harness and describing your task.

Frequently Asked Questions about acp-router

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

FAQPage Schema

How does multi-agent orchestration route requests to heterogeneous agents?▼

Agent routing determines the best agentId from user intent and spawns an ACPX child session via acp_spawn. It then coordinates subsequent actions using acp_send and maintains transport awareness to ensure reliable multi-agent orchestration.

How do I manage ACPX session lifecycles for one-shot and deterministic interactions?▼

Use acp_spawn to start a session, acp_send to dispatch task messages, and acp_kill to terminate it. This lifecycle management supports both deterministic sessions and one-shot interactions across heterogeneous agents.

Can I route tasks to specific coding agents like Claude, Cursor, or Codex?▼

Yes, the router maps user intent to specific harnesses including Claude, Cursor, Codex, Copilot, Gemini, Qwen, and others. It selects the best agentId and spawns a dedicated child session for the chosen agent.

What is the best way to handle errors during cross-agent task routing?▼

The best way to handle routing errors is to rely on the router's built-in transport awareness and robust error handling mechanisms. It safely manages agentId selection and orchestration to prevent failures across heterogeneous agents.

Why does acp_spawn fail to maintain deterministic sessions across multiple agents?▼

Deterministic sessions fail when transport awareness is lost or error handling is bypassed during multi-agent orchestration. Coordinating acp_spawn with acp_send and acp_kill ensures reliable session lifecycle management and prevents failures.