acp-router

Routes plain-language requests to ACP harnesses for session orchestration and recovery workflows.

1.0k|59|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill acp-router-safeai-lab-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/SafeAI-Lab-X/ClawKeeper/tree/main/legacy/clawkeeper-watcher/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill acp-router-safeai-lab-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests to ACP harness backends for correct session orchestration.

Core Features & Use Cases

  • OpenClaw ACP runtime path: use sessions_spawn with runtime acp, thread true, mode session. Do not use message with action=thread-create.
  • Direct acpx path (telephone game): drive harness sessions via the acpx CLI; reuse a stable session name; prefer --format quiet; provide deterministic behavior across prompts.
  • Thread spawn recovery and safety policies: in case of ACP backend failures, automatically repair locally by ensuring pinned acpx in extensions/acpx, restarting the gateway, and retrying once; avoid defaulting to global acpx.
  • Note: This list documents behavior described in the skill.

Quick Start

Invoke the acp-router skill to route your task through the ACP runtime or the direct acpx workflow.

Frequently Asked Questions about acp-router

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

FAQPage Schema
How do I route plain-language requests to ACP harness sessions?

To route requests to ACP harness sessions, you can use the OpenClaw ACP runtime path with sessions_spawn or drive the direct acpx CLI workflow for deterministic session orchestration and thread management.

What is the difference between the OpenClaw ACP runtime path and the direct acpx flow?

The OpenClaw ACP runtime path uses sessions_spawn with runtime acp and mode session, while the direct acpx flow drives harness sessions via the acpx CLI using a stable session name and quiet format for deterministic behavior.

How do I recover when ACP backends fail during thread spawn?

To recover from ACP backend failures, ensure the pinned acpx is installed in extensions/acpx, restart the gateway, and retry the thread spawn once, avoiding defaulting to the global acpx installation.

Can I use message with action=thread-create for ACP session orchestration?

No, for ACP session orchestration you should not use message with action=thread-create; instead, use sessions_spawn with runtime acp, thread true, and mode session to correctly manage the thread lifecycle.

What's the best way to maintain a stable session when using the acpx telephone-game flow?

To maintain a stable session with the acpx flow, reuse a stable session name across prompts and prefer the --format quiet flag to provide deterministic behavior throughout the harness session lifecycle.

Do I need to install acpx locally to use ACP routing policies?

Yes, local acpx installation and restart workflows are required for policy-driven routing, specifically to pin the correct acpx version in extensions/acpx and maintain seamless operation during backend recovery.