#`acpx`
10 messages · Page 1 of 1 (latest)
You usually don’t need to install acpx manually anymore.
Fresh OpenClaw installs ship the bundled acpx runtime plugin enabled by default, so start with:
openclaw acp doctor
If acpx was disabled or denied, use the documented recovery path:
openclaw plugins install acpx
openclaw config set plugins.entries.acpx.enabled true
openclaw gateway restart
openclaw acp doctor
So, short version: use openclaw plugins install acpx, not acpx@latest. The bundled plugin manages its own pinned acpx binary.
Docs:
If it’s still failing, paste:
openclaw --version
openclaw plugins list
openclaw acp doctor
❯ openclaw acp doctor
error: too many arguments for 'acp'. Expected 0 arguments but got 1.
Yep, that specific command is the problem.
openclaw acp is the ACP bridge CLI, not the ACP runtime control command, so:
openclaw acp doctor
will error.
Use this split instead:
openclaw plugins install acpx
openclaw config set plugins.entries.acpx.enabled true
openclaw gateway restart
Then:
- in chat:
/acp doctor - in shell:
openclaw plugins listandopenclaw status
So the docs are mixing two surfaces a bit:
openclaw acp→ CLI bridge for editors/ACP clients/acp doctor→ chat command for ACP runtime diagnostics
Docs:
If you want, paste these next and I’ll help decode them:
openclaw --version
openclaw plugins list
openclaw status