romtuck/openclaw
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Discord: fix DM recipient parsing for bare numeric user IDs (#596)

Browse Source 
Co-authored-by: Shadow <shadow@clawd.bot>
This commit is contained in:
Magi MetalandShadow authored and GitHub committed 2026-01-09 12:58:25 -06:00
1 parent 04512ee67c
commit 50a5b4ddcc
8 files changed
+24 -5
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/gateway/configuration.md
+1 -1
View File
@@ -765,7 +765,7 @@ Multi-account support lives under `discord.accounts` (see the multi-account sect
}
```
Clawdbot 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.
Clawdbot 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; bare numeric IDs are ambiguous and rejected.
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.