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

refactor: unify approval command authorization

Browse Source
This commit is contained in:
Peter Steinberger
2026-03-30 07:05:54 +09:00
parent 6ca81f8ec7
commit 6d9a7224aa
7 changed files with 141 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tools/exec-approvals.md
View File

@@ -401,16 +401,16 @@ originating chat can already send commands and receive replies, approval request
separate channel-specific approval client just to stay pending.
Discord and Telegram also support same-chat `/approve`, but those channels still use their
resolved approver list for authorization even when the richer approval client is disabled.
resolved approver list for authorization even when native approval delivery is disabled.
### Rich approval clients
### Native approval delivery
Discord and Telegram can also act as richer exec approval clients with channel-specific config.
Discord and Telegram can also act as native approval-delivery adapters with channel-specific config.
- Discord: `channels.discord.execApprovals.*`
- Telegram: `channels.telegram.execApprovals.*`
These richer clients are opt-in. They add native DM routing, channel fanout, and interactive UI on
These native delivery adapters are opt-in. They add DM routing, channel fanout, and interactive UI on
top of the shared same-chat `/approve` flow.
Shared behavior: