feat: unify provider reaction tools

docs/providers/discord.md

@@ -33,6 +33,8 @@ Status: ready for DM and guild text channels via the official Discord bot gatewa
     - Full command list + config: [Slash commands](/tools/slash-commands)
 11. Optional guild context history: set `discord.historyLimit` (default 20) to include the last N guild messages as context when replying to a mention. Set `0` to disable.
 12. Reactions: the agent can trigger reactions via the `discord` tool (gated by `discord.actions.*`).
+    - `emoji=""` removes the bot's reaction(s) on the message.
+    - `remove: true` removes the specific emoji reaction.
     - The `discord` tool is only exposed when the current provider is Discord.
 13. Native commands use isolated session keys (`discord:slash:${userId}`) rather than the shared `main` session.
 

docs/providers/slack.md

@@ -222,4 +222,5 @@ Slack tool actions can be gated with `slack.actions.*`:
 ## Notes
 - Mention gating is controlled via `slack.channels` (set `requireMention` to `true`); `routing.groupChat.mentionPatterns` also count as mentions.
 - Reaction notifications follow `slack.reactionNotifications` (use `reactionAllowlist` with mode `allowlist`).
+- For the Slack tool, `emoji=""` removes the bot's reaction(s) on the message; `remove: true` removes a specific emoji reaction.
 - Attachments are downloaded to the media store when permitted and under the size limit.

docs/providers/telegram.md

@@ -69,6 +69,12 @@ Telegram supports optional threaded replies via tags:
 Controlled by `telegram.replyToMode`:
 - `off` (default), `first`, `all`.
 
+## Agent tool (reactions)
+- Tool: `telegram` with `react` action (`chatId`, `messageId`, `emoji`).
+- `emoji=""` removes the bot's reaction(s) on the message.
+- `remove: true` removes the reaction (Telegram only supports removing your own reaction).
+- Tool gating: `telegram.actions.reactions` (default: enabled).
+
 ## Delivery targets (CLI/cron)
 - Use a chat id (`123456789`) or a username (`@name`) as the target.
 - Example: `clawdbot send --provider telegram --to 123456789 "hi"`.
@@ -92,6 +98,7 @@ Provider options:
 - `telegram.webhookUrl`: enable webhook mode.
 - `telegram.webhookSecret`: webhook secret (optional).
 - `telegram.webhookPath`: local webhook path (default `/telegram-webhook`).
+- `telegram.actions.reactions`: gate Telegram tool reactions.
 
 Related global options:
 - `routing.groupChat.mentionPatterns` (mention gating patterns).

docs/providers/whatsapp.md

@@ -94,6 +94,13 @@ WhatsApp requires a real mobile number for verification. VoIP and virtual number
 - WhatsApp Web sends standard messages (no quoted reply threading in the current gateway).
 - Reply tags are ignored on this provider.
 
+## Agent tool (reactions)
+- Tool: `whatsapp` with `react` action (`chatJid`, `messageId`, `emoji`, optional `remove`).
+- Optional: `participant` (group sender), `fromMe` (reacting to your own message), `accountId` (multi-account).
+- `emoji=""` removes the bot's reaction(s) on the message.
+- `remove: true` removes the bot's reaction (same effect as empty emoji).
+- Tool gating: `whatsapp.actions.reactions` (default: enabled).
+
 ## Outbound send (text + media)
 - Uses active web listener; error if gateway not running.
 - Text chunking: 4k max per message.
@@ -131,6 +138,7 @@ WhatsApp requires a real mobile number for verification. VoIP and virtual number
 - `whatsapp.groupAllowFrom` (group sender allowlist).
 - `whatsapp.groupPolicy` (group policy).
 - `whatsapp.groups` (group allowlist + mention gating defaults; use `"*"` to allow all)
+- `whatsapp.actions.reactions` (gate WhatsApp tool reactions).
 - `routing.groupChat.mentionPatterns`
 - `routing.groupChat.historyLimit`
 - `messages.messagePrefix` (inbound prefix)