diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index b4022e054..e3bf56106 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "ce1cd26fbcb04e2a9072efc89290065abc1bf20d", - "syncedAt": "2026-04-05T19:37:28.380Z" + "sha": "8a987030c0f416540d39c170df042756b9c92f0d", + "syncedAt": "2026-04-05T20:16:35.940Z" } diff --git a/docs/.generated/config-baseline.sha256 b/docs/.generated/config-baseline.sha256 index f0ed87132..1c5d1b521 100644 --- a/docs/.generated/config-baseline.sha256 +++ b/docs/.generated/config-baseline.sha256 @@ -1,4 +1,4 @@ -ff04a708e3d7f60c62f9347693c1e8b029748511f243e0c38fe32f47197fced5 config-baseline.json -717e2f414bbe7673404d89aea8d48cdf4acd7df92b67ba033ae9fa194651f3bb config-baseline.core.json -3c999707b167138de34f6255e3488b99e404c5132d3fc5879a1fa12d815c31f5 config-baseline.channel.json -317e1009e0d09c8d4fce0a415b15700e7043a5e7be75c38e4aaec02bb875dc9c config-baseline.plugin.json +57a3b1cc7d573c3788a670d927eac947fb1685384804f5c3c926f702a27fe00b config-baseline.json +82163136ff466db3caa61290fd65a8b8dd9487fc61f3871c177f96fcecf9e29b config-baseline.core.json +ae67508350baf891b902348d55fada6c17e9c053adf53aaf3a8b92cd364ef3f1 config-baseline.channel.json +d972a11d0f86080a722bddfe48990dd1b8fa16eb8e157e83f49bd46a5941c512 config-baseline.plugin.json diff --git a/docs/channels/discord.md b/docs/channels/discord.md index 195296383..7fa098d45 100644 --- a/docs/channels/discord.md +++ b/docs/channels/discord.md @@ -571,8 +571,14 @@ Default slash command settings: - `off` (default) - `first` - `all` + - `batched` Note: `off` disables implicit reply threading. Explicit `[[reply_to_*]]` tags are still honored. + `first` always attaches the implicit native reply reference to the first outbound Discord message for the turn. + `batched` only attaches Discord's implicit native reply reference when the + inbound turn was a debounced batch of multiple messages. This is useful + when you want native replies mainly for ambiguous bursty chats, not every + single-message turn. Message IDs are surfaced in context/history so agents can target specific messages.