@@ -39,10 +39,15 @@ directly to existing OpenClaw channel conversations, use
39394040## Does this work out of the box?
414142-Usually yes. Fresh installs ship the bundled `acpx` runtime plugin enabled
43-by default with a plugin-local pinned `acpx` binary that OpenClaw probes
44-and self-repairs immediately after the Gateway HTTP listener is live. Run
45-`/acp doctor` for a readiness check.
42+Yes, after installing the official ACP runtime plugin:
43+44+```bash
45+openclaw plugins install @openclaw/acpx
46+openclaw config set plugins.entries.acpx.enabled true
47+```
48+49+Source checkouts can use the local `extensions/acpx` workspace plugin after
50+`pnpm install`. Run `/acp doctor` for a readiness check.
46514752OpenClaw only teaches agents about ACP spawning when ACP is **truly
4853usable**: ACP must be enabled, dispatch must not be disabled, the current
@@ -53,8 +58,8 @@ an unavailable backend.
53585459<AccordionGroup>
5560<Accordion title="First-run gotchas">
56-- If `plugins.allow` is set, it is a restrictive plugin inventory and **must** include `acpx`; otherwise the bundled default is intentionally blocked and `/acp doctor` reports the missing allowlist entry.
57-- The bundled Codex ACP adapter is staged with the `acpx` plugin and launched locally when possible.
61+- If `plugins.allow` is set, it is a restrictive plugin inventory and **must** include `acpx`; otherwise the installed ACP backend is intentionally blocked and `/acp doctor` reports the missing allowlist entry.
62+- The Codex ACP adapter is staged with the `acpx` plugin and launched locally when possible.
5863- Other target harness adapters may still be fetched on demand with `npx` the first time you use them.
5964- Vendor auth still has to exist on the host for that harness.
6065- If the host has no npm or network access, first-run adapter fetches fail until caches are pre-warmed or the adapter is installed another way.
@@ -86,7 +91,7 @@ should call those tools directly.
86918792## Supported harness targets
889389-With the bundled `acpx` backend, use these harness ids as `/acp spawn <id>`
94+With the `acpx` backend, use these harness ids as `/acp spawn <id>`
9095or `sessions_spawn({ runtime: "acp", agentId: "<id>" })` targets:
91969297| Harness id | Typical backend | Notes |
@@ -232,7 +237,7 @@ See also [Sub-agents](/tools/subagents).
232237For Claude Code through ACP, the stack is:
2332382342391. OpenClaw ACP session control plane.
235-2. Bundled `acpx` runtime plugin.
240+2. Official `@openclaw/acpx` runtime plugin.
2362413. Claude ACP adapter.
2372424. Claude-side runtime/session machinery.
238243此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。