Skip to main content
The Discord adapter routes direct messages, mentions, and replies into the Entity runtime. It does not create an independent identity or memory store.

​
Configure the bot

Create a Discord application and bot in the Developer Portal. Configure the message permissions and intents required for the channels where it should operate, including access to message content for this adapter. Store the bot token privately as DISCORD_TOKEN. Add the platform to your Entity:
Start the runtime:
Send a direct message or mention the bot in an allowed server channel. The adapter also recognizes replies to the bot. It ignores messages from bots, including itself.

​
Channels and proactive delivery

The platform configuration supports a channels list and a proactive_channel_id. Set these to the intended Discord channel identifiers in private deployment configuration. A proactive destination is an outbound route. Confirm it before enabling autonomous work or routines that can send messages there.

​
Media and identity

Supported image and audio attachments can be included in Entity input. Provider and media-processing support still determine what the Entity can perceive. Discord supplies a platform person identifier and display name. Map the intended canonical person when connecting another surface; identical display names alone do not establish shared identity.

​
Operate the shared Entity

Telegram slash commands are not automatically Discord commands. Use the spatial inference control or a configured Telegram operator to pause the shared Entity, or stop its worker on the host. If text works but files, media, or tool effects do not, inspect the relevant backend separately. See troubleshooting.