Discord
Discord connects Fased through the official Discord bot APIs. Use it when you want a public bot identity, DMs, server channels, slash commands, and mention-gated team routing. Status: supported for DMs and guild channels.Pairing
DMs start with pairing unless you choose another policy.
Groups
Group policy, mentions, and sender controls.
Troubleshooting
Cross-channel checks and repair steps.
Quick setup
- Create a Discord application in the Discord Developer Portal.
- Add a Bot user.
- Enable Message Content Intent. Enable Server Members Intent only if you need role allowlists or name-to-ID matching.
- Invite the bot with
botandapplications.commandsscopes. - Open Agents > selected Agent > Channels > Discord.
- Paste the bot token, server id, and owner/user id.
- Save, start or restart the gateway, then pair the first DM if using pairing.
Access model
| Area | Recommended start |
|---|---|
| DMs | dmPolicy: "pairing" |
| Servers | groupPolicy: "allowlist" |
| Mentions | required in shared channels |
| Commands | owner or allowlist first |
| Agent routing | route server/channel/thread to the selected Agent explicitly |
Runtime behavior
- DMs and guild messages route into Agent sessions.
- Threads and forum channels keep their own session shape.
- Slash commands use the same command authorization path as other channels.
- Task commands create Agent-owned Tasks; Discord does not own the task.
- Delivery can return to the same channel/thread or an explicit target.
Useful commands
Troubleshooting
| Symptom | Check |
|---|---|
| Bot sees no messages | Message Content Intent, invite scopes, channel permissions. |
| DMs do not work | Server privacy setting, pairing state, DM policy. |
| Server messages ignored | Group policy, mention requirement, allowlists. |
| Slash commands missing | applications.commands scope and command registration logs. |
| Role routing fails | Server Members Intent and stable role/user ids. |