ACP Router v1.0 — Release Notes
Released: 2026-05-16
Security cleared: 2026-05-16 — Viper APPROVED_FOR_RELEASE; Security Audit CLEARED by Warlock
Category: orchestration
Price: $4.99
What it does
ACP Router helps OpenClaw operators choose the right execution path for a task: native tools, browser automation, coding sessions, ACP harness runs, or persistent ACP sessions. It turns messy routing decisions into a clear recommendation with risk level, confidence, persistence, and approval requirements so teams can delegate work without bypassing safety gates.
It is especially useful when users ask for Claude Code, Cursor, Gemini, Codex ACP, or another harness and the agent needs to decide whether to run once, open a persistent session, or ask for human approval first.
Use cases
- Agent operators routing coding work: decide whether a repo task should stay in native tools, move to a coding session, or run through an ACP harness.
- Discord/Telegram workflow owners: keep long-running or thread-bound ACP requests consistent across chat channels without manually rebuilding routing rules.
- Governed automation teams: flag destructive, production, credential, Stripe, deploy, publish, or config tasks as approval-required before an agent acts.
Requirements
- OpenClaw: compatible with current ACP/session-spawn workflows and standard skill layout.
- Runtime: Python 3.8+.
- Dependencies: Python standard library only.
- API keys: none required.
- Optional inputs: preferred harness/agent name and channel (
telegram,discord, orcli) for better routing context.
Example usage
python3 skills/acp-router/scripts/acp_router.py \
--task "run this repo fix in Claude Code and keep a Discord thread" \
--agent "claude code" \
--channel discord \
--json
Expected output
{
"route": "acp_session",
"risk": "medium",
"confidence": "high",
"explicit_acp": true,
"persistent": true,
"approval_required": false,
"notes": [
"Use ACP session spawn path; set agentId explicitly when required.",
"Prefer thread-bound persistent ACP session on Discord.",
"Proceed with smallest verification gate before reporting success."
]
}
QA and security context
Viper test results on 2026-05-16 passed 7/7 checks and marked acp-router as APPROVED_FOR_RELEASE. Warlock security audit cleared the skill; grep found no eval, exec, subprocess, network, credential, or exfiltration patterns, and the generic security audit did not list the skill in red/yellow review sets.
Marketing copy
ACP Router gives OpenClaw teams a simple, auditable way to decide where work should run: native tools, browser automation, coding sessions, one-shot ACP runs, or persistent harness sessions. It recognises explicit Claude Code, Cursor, Gemini, Codex ACP and other harness requests, flags risky production or credential work for approval, and returns clean JSON routing guidance operators can trust.