Connect Discord to Your Super Agent

Before You Start

Use this guide for a hosted Super Agent. You need permission to manage that agent, permission to add a bot to the Discord server, and a Discord account that can open the Discord Developer Portal.

Decide which people and channels may reach the agent before setup. Start with your own Discord user ID and one test channel, then widen access after the first message works.

Treat the Discord bot token like a password. Agentic Workers encrypts it when you save the connection and does not show it again. Never paste it into agent chat, a support message, a screenshot, or source control.

1. Create the Discord Bot

Open the Discord Developer Portal, choose New Application, and give the application a clear name. Open Bot in the application menu and create the bot if Discord has not already created one.

On the Bot page, turn on Server Members Intent and Message Content Intent. Message Content Intent is required so the Super Agent can read the message text it receives.

Keep Requires OAuth2 Code Grant off for this bot connection. Under Token, choose Reset Token or Copy Token and keep the value in a password manager until you enter it in Agentic Workers.

2. Add the Bot to Your Server

In the Developer Portal, open OAuth2, then URL Generator. Select the bot and applications.commands scopes.

Give the bot only the permissions it needs: View Channels, Send Messages, Create Public Threads, Send Messages in Threads, Read Message History, Embed Links, Attach Files, and Add Reactions. Server or channel administrators can narrow those permissions further.

Open the generated authorization link, choose the intended Discord server, and approve the install. Confirm the bot appears in the server member list before continuing.

3. Copy Your Discord User ID

In Discord, open User Settings, choose Advanced, and turn on Developer Mode. Right-click your profile or username and choose Copy User ID.

Use numeric user IDs for access control, not display names or server nicknames. Add each approved person separately in Agentic Workers, separated by commas.

To copy a channel ID, right-click the channel and choose Copy Channel ID. You only need channel IDs when you want a channel where the bot may answer without an @mention.

4. Connect Discord in Agentic Workers

Open the hosted Super Agent, choose Gateways, then choose Discord. Paste the bot token and add at least one Allowed Discord user ID.

Keep Require @mention in server channels on for the safest first test. Direct messages from approved users do not require a mention. Free-response channel IDs are optional and let the bot answer inline without a mention in only those channels.

Keep separate sessions per user on when several people share a channel. This prevents one person's conversation from becoming another person's context. Turn on the thread mention option when multiple bots share the same Discord threads.

Choose Connect Discord. The status moves through applying or configured while the hosted agent restarts, then shows Connected when the Discord connection is active.

5. Verify the First Message

In a server channel the bot can view, mention the bot and send a small request such as "What can you help with here?" The Super Agent normally opens or continues a Discord thread so the channel stays readable.

Confirm the reply appears under the bot identity and that follow-up messages stay in the same thread. If you kept thread mentions optional, an approved user can continue inside that thread without mentioning the bot again.

Run one low-risk tool check before using the connection for real work. Review the latest trace, the step-by-step run log, in Agentic Workers if you need to confirm which agent, tool, or workspace handled the request.

Access and Session Controls

Allowed user IDs are enforced for direct messages, server channels, and threads. A person who is present in the Discord server but is not on the allowed list cannot use the agent.

Require @mention limits new server-channel requests to messages that name the bot. Free-response channels are the deliberate exception, so use them only where every message should be eligible for a response.

Separate sessions per user keeps shared-channel context isolated across communication channels. Leave it on unless your workflow intentionally needs one shared conversation for everyone.

Troubleshooting

If status shows an error, confirm the bot token is current, the bot is still installed in the server, and both Server Members Intent and Message Content Intent are enabled. Reset the token in Discord, enter the new token in Agentic Workers, and try again if the old token may have been exposed or revoked.

If the bot is connected but does not answer, confirm your numeric Discord user ID is on the allowed list and mention the bot in the first server-channel message. Then check that the bot can view the channel, send messages, read message history, create threads, and send messages in threads.

If the bot works in one channel but not another, review that channel's role and member permission overrides. Discord channel overrides can block the bot even when its server role has the right permissions.

If follow-up messages in a thread are ignored, mention the bot again or turn off Require @mention on every thread message. If replies mix context between people, turn separate sessions per user back on and start a fresh thread.

If status stays configured while the bot is still starting, wait a moment and refresh. If it remains there, save the settings again to retry the hosted agent restart, then contact support with the workspace, agent name, timestamp, and visible status. Never send the bot token.

Rotate or Remove the Connection

To rotate the credential, reset the token on the Discord Bot page, enter the new token in the Discord settings for the Super Agent, and choose Update Discord. Test one message after the status returns to Connected.

Choose Remove Discord when the agent should no longer use the bot. Agentic Workers permanently removes the stored bot token and settings from that agent, then restarts the hosted connection.

Also remove the bot from the Discord server or delete the Discord application when it is no longer needed. Review the allowed-user and channel lists whenever teammates or server roles change.