acp-router

Routing plain-language coding requests to the correct ACP harness is handled by intent-driven flow routing. It analyzes user intent and system state to automatically select the ACP runtime path or direct acpx flow.

Intent-driven routing maps requests to a specific agentId using consistent default mappings for common harness names. This ensures your prompts reach the correct agent, such as pi, claude, codex, opencode, gemini, or kimi.

You can reuse deterministic sessions for multi-turn tasks in ACP. The system creates sessions via sessions_spawn, preserving deterministic session names to maintain thread-safe continuity across multiple interactions.

The ACP router supports built-in recovery when the preferred runtime path is unavailable. If the ACP runtime path fails, it automatically falls back to relay prompts via direct acpx to maintain workflow.

Preflight checks for coding-agent thread requests enforce validation rules before routing. This ensures the target runtime and agentId are properly configured before initiating the ACP session creation process.

Use the ACP runtime path for full session management and multi-turn tasks, while direct acpx flow is used for relaying prompts when the runtime is unavailable or for simpler routing scenarios.