let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: clarify discord reaction notifications

Browse Source
This commit is contained in:
Shadow
2026-01-03 12:31:50 -06:00
committed by Peter Steinberger
parent 451174ca10
commit 7abd6713c8
2 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/configuration.md
View File

@@ -281,6 +281,11 @@ Configure the Discord bot by setting the bot token and optional gating:
Clawdis starts Discord only when a `discord` config section exists. The token is resolved from `DISCORD_BOT_TOKEN` or `discord.token` (unless `discord.enabled` is `false`). Use `user:<id>` (DM) or `channel:<id>` (guild channel) when specifying delivery targets for cron/CLI commands.
Guild slugs are lowercase with spaces replaced by `-`; channel keys use the slugged channel name (no leading `#`). Prefer guild ids as keys to avoid rename ambiguity.
Reaction notification modes:
- `off`: no reaction events.
- `own`: all reactions on the bot's own messages.
- `all`: all reactions on all messages.
- `allowlist`: reactions from `guilds.<id>.users` on all messages.
### `imessage` (imsg CLI)

6
docs/discord.md
View File

@@ -119,7 +119,11 @@ Note: Guild context `[from:]` lines include `author.tag` + `id` to make ping-rea
- `roles` (role add/remove, default `false`)
- `moderation` (timeout/kick/ban, default `false`)
Reaction notifications use `guilds.<id>.reactionNotifications`; `allowlist` checks `guilds.<id>.users`, while `all` ignores that allowlist.
Reaction notifications use `guilds.<id>.reactionNotifications`:
- `off`: no reaction events.
- `own`: all reactions on the bot's own messages.
- `all`: all reactions on all messages.
- `allowlist`: reactions from `guilds.<id>.users` on all messages.
### Tool action defaults