vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-04-30 14:20:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor(acp): centralize conversation binding context

Browse Source
This commit is contained in:
Peter Steinberger
2026-03-28 03:46:17 +00:00
parent 09e35e69b2
commit d0d4b73d25
5 changed files with 505 additions and 107 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -3,7 +3,7 @@ summary: "Use ACP runtime sessions for Codex, Claude Code, Cursor, Gemini CLI, O
read_when:
- Running coding harnesses through ACP
- Setting up conversation-bound ACP sessions on messaging channels
- Binding Discord channels, Telegram topics, BlueBubbles chats, or iMessage chats to persistent ACP sessions
- Binding a message channel conversation to a persistent ACP session
- Troubleshooting ACP backend and plugin wiring
- Operating /acp commands from chat
title: "ACP Agents"
@@ -104,12 +104,11 @@ Examples:
- `/acp spawn codex --thread auto`: OpenClaw may create a child thread/topic and bind the ACP session there
- `/acp spawn codex --bind here --cwd /workspace/repo`: same chat binding as above, but Codex runs in `/workspace/repo`
Built-in current-conversation binding support:
Current-conversation binding support:
- Discord current channel or current thread
- Telegram current chat or current topic
- BlueBubbles DM or group chat
- iMessage DM or group chat
- Any message channel can use `--bind here` through the shared conversation-binding path.
- Channels with custom thread/topic semantics can still provide channel-specific canonicalization behind the same shared interface.
- `--bind here` always means "bind the current conversation in place"; it does not require a per-channel ACP adapter anymore.
Notes: