acp-router

To route ACP harness tasks, the router detects intent and selects the appropriate path, directing requests to OpenClaw ACP runtime sessions or direct acpx flows. It enforces preflight checks before spawning any threads.

Sessions_spawn handles thread creation by spawning new runtime sessions within the OpenClaw ACP path. It maps agents explicitly during the routing process to ensure tasks reach the correct backend.

Multi-backend routing for coding-agent threads is managed by detecting task intent and selecting the proper runtime path. The router enforces preflight checks and uses sessions_spawn to create threads across various ACP harness backends.

ACPX install or version failures are addressed by the router's codified recovery policies and fallback options. The router enforces version checks and provides fallback paths to maintain workflow continuity when direct acpx flows encounter issues.

Yes, preflight checks are required before routing to a direct acpx flow. The router enforces these checks to validate the runtime environment and ensure session management policies are met before task execution.

Yes, you can use the ACP router for session management across various harness backends. It selects runtime paths, uses sessions_spawn for thread creation, and applies explicit agent mapping to manage sessions effectively.