Discord is a deployment-owned communications provider. It is not a Roomote
sign-in provider.
Roomote can receive direct messages and server mentions, work each task in a
thread on the message that requested it (or a forum post in forum channels),
accept follow-ups in that conversation, and deliver onboarding suggestions to
the default channel. Discord connects to Roomote through the Gateway, so it
does not require an inbound webhook or public callback URL.
Create the Discord bot
- Open the Discord Developer Portal
and create an application.
- Open Bot, create the bot if needed, and copy or reset its token.
- Under Privileged Gateway Intents, enable Message Content Intent.
Roomote needs this to understand natural-language messages and follow-ups.
- In Roomote, open Settings > Communications > Discord, paste the bot
token, and save.
Roomote reads the bot and application identity from the token and registers
the /new, /link, and /help commands automatically. You do not need to
copy an application ID or bot name into Roomote.
Treat the bot token like a password. Do not put it in a repository, task
prompt, or Discord message.
Add Roomote to a server
After you save the bot token, the Add to Discord button appears in Roomote.
Select it and choose the server. The generated installation link requests the
permissions Roomote needs; administrator access is not required.
For tasks started in a server, the bot needs these permissions:
- view channels
- send messages
- read message history
- embed links
- attach files
- create public threads
- send messages in threads
- add reactions
- manage threads (only when a required-tag forum has no unmoderated tags)
A task started from a normal text or announcement channel runs in a public
thread started on the message that requested it — like a threaded reply — so
the conversation stays anchored where it began. A task started in a forum gets
its own forum post, and /new starts a fresh, separate task thread. When a
forum requires a tag, Roomote applies an available unmoderated tag
automatically. If every tag is moderated, the bot needs Manage Threads to
apply one.
Unlike a Slack workspace, a Discord server can be public or shared with
people outside your team. Task threads are visible to everyone who can see
the channel, including repository names, task descriptions, and PR links.
Only add Roomote to servers whose members you trust with that context, and
use private channels for sensitive work.
Link your account
Discord tasks are attributed only to people who have linked their Discord
account to a Roomote user.
Generate a link command under Settings > Personal > Linked Accounts and run
it in a direct message with the bot. This verifies that Roomote can reach you
for onboarding work. If Discord blocks the DM, open the server’s Privacy
Settings and enable Direct Messages. The command expires after ten
minutes. Once linked, work you start from Discord is attributed to your Roomote
account.
During onboarding, Roomote posts the setup suggestions to the default channel
so the whole team can see and start them. When no default channel is
configured yet, they are sent to the linked setup user’s direct messages
instead; Discord can block those messages when the user’s server-member DM
privacy setting is disabled, and the task remains available in the Roomote web
app in that case.
Default channel for proactive posts
Roomote posts proactive updates (automation suggestions, reports, and other
messages that are not replies to an existing conversation) to a default
channel you pick. Choose it in the Discord section of Roomote’s comms settings:
select a server and a text or forum channel where the bot has permission to
post and create threads. Replies always stay in the conversation they started
in. Required-tag forums work when Roomote can apply a usable tag — an
unmoderated tag, or a moderated tag when the bot has Manage Threads.
Individual automations can also report to their own Discord channel instead of
the default: pick a Discord channel in that automation’s destination selector
under Settings > Automations, the same way you would pick a Slack channel.
Start and continue tasks
- mention the bot with a request in a server channel
- mention the bot in a thread reply to start work in that same thread (Slack-
style), with earlier thread messages and supported attachments as context
- send the bot a direct message
- use
/new request:<request> to force a fresh task instead of continuing the
current one
- when Roomote asks where to run a task, use a button or reply naturally in the
same thread or DM;
yes, never mind, and use API instead confirm, cancel,
or revise the pending route
- reply naturally inside a task thread, forum post, or DM to continue it
(same Slack-style rules: after someone else posts or is @mentioned in the
thread since Roomote’s last reply, tag Roomote again to keep going)
- use
/help to see the available commands
Roomote does not quote every message it answers. In a task thread, the
conversation itself supplies the context. When you start a task by tagging
Roomote in an existing thread, Roomote reads earlier messages in that thread
(including supported attachments, up to a few hundred recent thread messages) so the agent
has that background. Follow-ups in an active or resumed task thread also carry
undelivered earlier Discord messages the same way Slack does, so the agent keeps
full thread context across turns. Natural follow-ups without an @mention work
for people already in the conversation with Roomote (the task owner, the thread
starter, or anyone who tagged Roomote earlier). If somebody else posts or is
mentioned after Roomote’s last reply, tag Roomote again so side chat is not
treated as a new instruction. Image attachments are passed to the task as
image input, and supported documents are downloaded and added to the request.
Attachment downloads are size-limited and restricted to Discord’s media hosts.
Self-hosted configuration
The setup UI stores the token for the deployment. To configure it with an
environment variable instead, set:
The Discord Gateway runs as an opt-in subsystem inside Roomote’s existing
BullMQ process, so enabling Discord does not add another container, process, or
port. It stays dormant until a token is saved, uses Redis to elect a single
active replica, and disconnects if Discord is removed. Durable event delivery
uses Redis and a dedicated internal shared secret. Saving Discord credentials in
settings generates R_DISCORD_GATEWAY_SECRET when it is not already configured.
If Discord was already set up without one (for example after an upgrade),
Roomote generates and persists the secret automatically the next time the
gateway or API needs it, or when you use Repair. For env-var-only setups,
set the same secret on the API and BullMQ processes yourself (installers and
platform templates also generate one).
Gateway session state is stored in the Roomote database. On a service restart
or leader handoff, Roomote asks Discord to resume the previous session and
replay any missed events; Discord can fall back to a fresh session when the old
one has expired.
Restart BullMQ after changing either environment variable. Tokens saved in the
setup UI are detected automatically without a restart.
Verify setup
- confirm the Discord settings page shows the bot identity and a connected
Gateway
- confirm Message Content intent and Slash commands pass their checks
- link your personal Discord account
- mention the bot with a small request and confirm Roomote creates a task
thread or forum post
- reply in that conversation and confirm the same task continues
If the Gateway remains disconnected, verify BullMQ is running and has access to
the same Redis, database, token, and internal secret as the API. If natural
messages are ignored but slash commands work, enable Message Content Intent in
the Developer Portal and restart BullMQ. 
