@@ -37,6 +37,7 @@ Usually, yes. Fresh installs ship the bundled `acpx` runtime plugin enabled by d
37373838First-run gotchas:
393940+- 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.
4041- Target harness adapters (Codex, Claude, etc.) may be fetched on demand with `npx` the first time you use them.
4142- Vendor auth still has to exist on the host for that harness.
4243- 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.
@@ -78,12 +79,14 @@ Natural-language triggers that should route to the ACP runtime:
78797980OpenClaw picks `runtime: "acp"`, resolves the harness `agentId`, binds to the current conversation or thread when supported, and routes follow-ups to that session until close/expiry. Codex only follows this path when ACP is explicit or the requested background runtime still needs ACP.
808181-For `sessions_spawn`, `runtime: "acp"` targets ACP harness ids such as `codex`,
82-`claude`, `gemini`, or `opencode`. Do not pass a normal OpenClaw config agent
83-id from `agents_list` unless that entry is explicitly configured with
84-`agents.list[].runtime.type="acp"`; otherwise use the default sub-agent runtime.
85-When an OpenClaw agent is configured with `runtime.type="acp"`, OpenClaw uses
86-`runtime.acp.agent` as the underlying harness id.
82+For `sessions_spawn`, `runtime: "acp"` is advertised only when ACP is enabled,
83+the requester is not sandboxed, and an ACP runtime backend is loaded. It targets
84+ACP harness ids such as `codex`, `claude`, `gemini`, or `opencode`. Do not pass
85+a normal OpenClaw config agent id from `agents_list` unless that entry is
86+explicitly configured with `agents.list[].runtime.type="acp"`; otherwise use
87+the default sub-agent runtime. When an OpenClaw agent is configured with
88+`runtime.type="acp"`, OpenClaw uses `runtime.acp.agent` as the underlying
89+harness id.
87908891## ACP versus sub-agents
8992@@ -551,7 +554,7 @@ plugin-tools and OpenClaw-tools MCP bridges, and ACP permission modes, see
551554552555| Symptom | Likely cause | Fix |
553556| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
554-| `ACP runtime backend is not configured` | Backend plugin missing or disabled. | Install and enable backend plugin, then run `/acp doctor`. |
557+| `ACP runtime backend is not configured` | Backend plugin missing, disabled, or blocked by `plugins.allow`. | Install and enable backend plugin, include `acpx` in `plugins.allow` when that allowlist is set, then run `/acp doctor`. |
555558| `ACP is disabled by policy (acp.enabled=false)` | ACP globally disabled. | Set `acp.enabled=true`. |
556559| `ACP dispatch is disabled by policy (acp.dispatch.enabled=false)` | Dispatch from normal thread messages disabled. | Set `acp.dispatch.enabled=true`. |
557560| `ACP agent "<id>" is not allowed by policy` | Agent not in allowlist. | Use allowed `agentId` or update `acp.allowedAgents`. |
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。