From c35712a9e0f86a0d5d44e31bd7f0fac6328ae548 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sun, 5 Apr 2026 14:31:10 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@0aaf7531481dd793eb521764f64efebdfe327be6 --- .openclaw-sync/source.json | 4 ++-- docs/channels/matrix.md | 8 +++++++- docs/tools/exec-approvals.md | 5 +++++ 3 files changed, 14 insertions(+), 3 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index c4f5c2e5e..906bc9d51 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "dfd39a81d8478da3a58f5d385c76c29ab7afcd8d", - "syncedAt": "2026-04-05T14:25:49.549Z" + "sha": "0aaf7531481dd793eb521764f64efebdfe327be6", + "syncedAt": "2026-04-05T14:31:10.299Z" } diff --git a/docs/channels/matrix.md b/docs/channels/matrix.md index 7e1c98555..543cff92b 100644 --- a/docs/channels/matrix.md +++ b/docs/channels/matrix.md @@ -679,7 +679,13 @@ Delivery rules: - `target: "channel"` sends the prompt back to the originating Matrix room or DM - `target: "both"` sends to approver DMs and the originating Matrix room or DM -Matrix uses text approval prompts today. Approvers resolve them with `/approve allow-once`, `/approve allow-always`, or `/approve deny`. +Matrix approval prompts seed reaction shortcuts on the primary approval message: + +- `✅` = allow once +- `❌` = deny +- `♾️` = allow always when that decision is allowed by the effective exec policy + +Approvers can react on that message or use the fallback slash commands: `/approve allow-once`, `/approve allow-always`, or `/approve deny`. Only resolved approvers can approve or deny. Channel delivery includes the command text, so only enable `channel` or `both` in trusted rooms. diff --git a/docs/tools/exec-approvals.md b/docs/tools/exec-approvals.md index c2331e155..0d139da44 100644 --- a/docs/tools/exec-approvals.md +++ b/docs/tools/exec-approvals.md @@ -24,6 +24,11 @@ host policy sources, and the effective result. If the companion app UI is **not available**, any request that requires a prompt is resolved by the **ask fallback** (default: deny). +Native chat approval clients can also expose channel-specific affordances on the +pending approval message. For example, Matrix can seed reaction shortcuts on the +approval prompt (`✅` allow once, `❌` deny, and `♾️` allow always when available) +while still leaving the `/approve ...` commands in the message as a fallback. + ## Where it applies Exec approvals are enforced locally on the execution host: