vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 19:31:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: keep acp management commands local

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-26 02:58:19 +01:00
parent 9123c8158d
commit a6d9926d1d
9 changed files with 199 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/tools/acp-agents.md
View File

@@ -150,6 +150,10 @@ Notes:
- `--bind here` only works on channels that advertise current-conversation binding; OpenClaw returns a clear unsupported message otherwise. Bindings persist across gateway restarts.
- On Discord, `spawnAcpSessions` is only required when OpenClaw needs to create a child thread for `--thread auto|here` — not for `--bind here`.
- If you spawn to a different ACP agent without `--cwd`, OpenClaw inherits the **target agent's** workspace by default. Missing inherited paths (`ENOENT`/`ENOTDIR`) fall back to the backend default; other access errors (e.g. `EACCES`) surface as spawn errors.
- Gateway management commands stay local in bound conversations. In
particular, `/acp ...` commands are handled by OpenClaw even when normal
follow-up text routes to the bound ACP session; `/status` and `/unfocus` also
stay local whenever command handling is enabled for that surface.
### Thread-bound sessions
@@ -159,6 +163,8 @@ When thread bindings are enabled for a channel adapter, ACP sessions can be boun
- Follow-up messages in that thread route to the bound ACP session.
- ACP output is delivered back to the same thread.
- Unfocus/close/archive/idle-timeout or max-age expiry removes the binding.
- `/acp close`, `/acp cancel`, `/acp status`, `/status`, and `/unfocus` are
Gateway commands, not prompts to the ACP harness.
Thread binding support is adapter-specific. If the active channel adapter does not support thread bindings, OpenClaw returns a clear unsupported/unavailable message.

5
docs/tools/slash-commands.md
View File

@@ -9,6 +9,11 @@ title: "Slash commands"
Commands are handled by the Gateway. Most commands must be sent as a **standalone** message that starts with `/`.
The host-only bash chat command uses `! <cmd>` (with `/bash <cmd>` as an alias).
When a conversation or thread is bound to an ACP session, normal follow-up text
routes to that ACP harness. Gateway management commands still stay local:
`/acp ...` always reaches the OpenClaw ACP command handler, and `/status` plus
`/unfocus` stay local whenever command handling is enabled for the surface.
There are two related systems:
- **Commands**: standalone `/...` messages.