docs(plugins): note cancelDelivered in channel plugin interactions list · openclaw/openclaw@a2f1f73
Feelw00
·
2026-05-16
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -158,7 +158,7 @@ Most channel plugins do not need approval-specific code.
|
158 | 158 | - `availability` - whether the account is configured and whether a request should be handled |
159 | 159 | - `presentation` - map the shared approval view model into pending/resolved/expired native payloads or final actions |
160 | 160 | - `transport` - prepare targets plus send/update/delete native approval messages |
161 | | -- `interactions` - optional bind/unbind/clear-action hooks for native buttons or reactions |
| 161 | +- `interactions` - optional bind/unbind/clear-action hooks for native buttons or reactions, plus an optional `cancelDelivered` hook. Implement `cancelDelivered` when `deliverPending` registers in-process or persistent state (such as a reaction target store) so that state can be released if a handler stop cancels the delivery before `bindPending` runs or when `bindPending` returns no handle |
162 | 162 | - `observe` - optional delivery diagnostics hooks |
163 | 163 | - If the channel needs runtime-owned objects such as a client, token, Bolt app, or webhook receiver, register them through `openclaw/plugin-sdk/channel-runtime-context`. The generic runtime-context registry lets core bootstrap capability-driven handlers from channel startup state without adding approval-specific wrapper glue. |
164 | 164 | - Reach for the lower-level `createChannelApprovalHandler` or `createChannelNativeApprovalRuntime` only when the capability-driven seam is not expressive enough yet. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
