Connect Your Agent to Discord

95% of the time this is the Message Content Intent.

Go to Discord Developer Portal → your application → Bot → scroll to Privileged Gateway Intents → make sure Message Content Intent is toggled ON → Save Changes.

Then tell your agent: "Restart the gateway" or just wait a minute for it to reconnect.

This is usually a policy/config mismatch — not a token failure.

Run this exact sequence in your dashboard chat:

1) "Add my Discord Server ID [your server ID] to the guild allowlist."
2) "Set Discord requireMention to false and groupPolicy to open."
3) "Set Discord allowBots to true." (needed if your workflow involves relays/other bot messages)
4) "Restart the gateway."

Then test in a brand-new text channel with default permissions. If it works there, your core setup is healthy and older channels likely have overrides/restrictions.

Check that you enabled DMs from server members (Step 8). Right-click your server icon → Privacy Settings → toggle Direct Messages ON.

Also make sure the bot is actually online in your server. If it shows offline, the token might be wrong or the gateway hasn't started. Ask your agent "Is Discord connected?" in the dashboard.

Pairing codes expire after 1 hour. If too much time has passed, DM the bot again to get a fresh code.

Make sure you're pasting the code exactly — no extra spaces. Tell your agent: "Approve this Discord pairing code: XXXX"

In rare cases, an agent can accidentally overwrite its own config during setup. If your agent stopped responding everywhere (including the web dashboard), you'll need support.

Open a ticket in #help on the heyron Discord with your signup email, and the team will fix your config server-side. This is a known edge case and they can usually resolve it in minutes.

The bot showing offline usually means the gateway hasn't connected yet. Tell your agent: "Restart the gateway" in the web dashboard.

If that doesn't work, double-check that your bot token is correct. You can regenerate it in the Developer Portal (Bot → Reset Token) and give the new token to your agent.

This is expected if your agent is configured to ask before sensitive actions. Read the full guide: Why Your Agent Says “Approval Required”.

Quick rule: approve only if the command matches what you're trying to do (Discord connect / gateway restart), and deny anything that looks unrelated.

If you denied a needed command by accident, just tell your agent to try again and approve the same safe action on the next prompt.

First, make sure your bot has View Channels, Send Messages, and Read Message History in the specific channel you're testing.

Then test in a brand-new channel with minimal custom permissions. Channel-level overrides are a common hidden blocker.

If it works in the new channel, the issue is channel permissions — not your token or intents.

This is usually a Discord integration restriction, stale session, or channel override issue.

Run this fast isolation flow:

1) In Discord: Server Settings → Integrations → your bot and confirm commands are allowed for your role/channel.
2) In heyron dashboard, start fresh with /new and ask your agent: "Restart the gateway and verify Discord is connected."
3) Create a brand-new channel with default permissions and test one message that @mentions the bot.
4) If mention works there but not elsewhere, fix per-channel overrides. If mention fails everywhere, regenerate token (Bot → Reset Token) and reconnect in dashboard.

Community pattern: many "bot won't reply" reports are not bad intents — they're integration restrictions or channel-level permission drift.

You're still talking to the same agent identity. Discord just gives you two conversation surfaces:

• DM = private one-on-one thread
• Server channels = group/public threads with separate channel context

If channel behavior feels different, it's usually one of these:

1) You're testing in a different channel (each channel has its own conversation history).
2) Channel permissions/overrides differ from DM behavior.
3) You accidentally created a second bot application/token during retries.

Quick check: in Discord Developer Portal, confirm you're using one app + one token; in heyron dashboard, ask your agent to report the active Discord app name and server ID, then test in a clean new channel with one @mention.

This pattern usually means read permissions are okay, but send permissions are blocked in that channel.

Check these in the exact channel you're testing:

1) Channel settings → Permissions: bot role has Send Messages allowed (not neutral/denied).
2) If channel is a Thread, also allow Send Messages in Threads.
3) If channel is a Forum, confirm the bot can create/reply to posts in that forum.
4) Server Settings → Integrations → your bot: command and channel restrictions are not blocking this channel.
5) Slowmode/mod rules are not preventing immediate replies from newly joined bots.

Known-good test: create a fresh text channel with default permissions, @mention the bot once. If it replies there, your core setup is fine and this is a channel-level policy issue.

Short answer: not reliably, and usually not recommended.

Most users mean "my Heyron bot + another bot should auto-chat." In practice, this creates loops, mention failures, and moderation/rate-limit issues. Many bots also ignore other bots by design.

If your goal is automation, better pattern:

1) Keep one primary Heyron bot for conversation.
2) Use connectors/tools for data handoff instead of bot-to-bot chatting.
3) Test with a human message + @mention first to confirm your Heyron bot is healthy.

If your Heyron bot responds to humans but not other bots, your setup is probably fine — that's expected behavior, not a broken connection.

You need admin permissions on the server to add a bot. If you're a regular member, ask the server owner to add your bot using the invite URL from Step 5.

For most use cases, we recommend creating your own private server. It's free and takes 30 seconds.