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

matrix-js: require explicit thread-bound spawn config

Browse Source
This commit is contained in:
Gustavo Madeira Santana
2026-03-08 19:20:57 -04:00
parent 96d7e4552d
commit a54aa338cd
12 changed files with 286 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/gateway/configuration-reference.md
View File

@@ -651,6 +651,7 @@ Run multiple accounts per channel (each with its own `accountId`):
### Other extension channels
Many extension channels are configured as `channels.<id>` and documented in their dedicated channel pages (for example Feishu, Matrix, LINE, Nostr, Zalo, Nextcloud Talk, Synology Chat, and Twitch).
Matrix-js also supports top-level `bindings[]` entries with `type: "acp"` for persistent ACP bindings. Use the Matrix room id or Matrix thread root event id in `match.peer.id`.
See the full channel index: [Channels](/channels).
### Group chat mention gating
@@ -1453,7 +1454,7 @@ Run multiple isolated agents inside one Gateway. See [Multi-Agent](/concepts/mul
Within each tier, the first matching `bindings` entry wins.
For `type: "acp"` entries, OpenClaw resolves by exact conversation identity (`match.channel` + account + `match.peer.id`) and does not use the route binding tier order above.
For `type: "acp"` entries, OpenClaw resolves by exact conversation identity (`match.channel` + account + `match.peer.id`) and does not use the route binding tier order above. For example, use a Discord channel/thread id, a Matrix room id or thread root event id, or a Telegram canonical topic id.
### Per-agent access profiles