acp-router

To route user requests to the correct OpenClaw ACP harness path, the acp-router detects user intent and directs prompts to either the runtime or direct acpx flow. It applies preflight checks and maps agent names to ensure accurate routing for coding-harness tasks.

Agent ID mapping for ACP harness thread spawning works by translating common harness names like pi, codex, and claude into consistent agent IDs. The router uses these mappings to enforce preflight checks and direct session handling across multiple backends.

Yes, you can use acp-router for session lifecycle management across multiple backends. It handles session spawning, thread creation, and mode parameters automatically, applying safe fallback guidance to prevent unsafe harness usage during runtime or direct acpx flows.

The best way to execute coding-harness tasks using direct acpx flows is through explicit runtime selection with preflight checks. The router directs prompts to the correct backend session, handling thread spawning and agent-name mappings to ensure safe and consistent execution.

ACP harness routing requires preflight checks before thread creation to enforce safe thread spawning guidelines and avoid unsafe harness usage. These checks validate runtime selection and session parameters, ensuring correct session handling and preventing errors across backend flows.

Yes, acp-router supports both runtime and direct acpx execution modes. It implements explicit runtime selection based on detected user intent, applying preflight checks and safe fallback guidance to route coding-harness tasks to the appropriate execution path.