Connect Discord to Hermes Agent: Bot Setup Checklist
Connect Discord to Hermes Agent with a short Developer Portal, bot token, intent, channel permission, gateway restart, and verification checklist.
Quick answer
Create a Discord application and bot, enable the required intent, invite it with bot plus applications.commands scopes, add the token to the Hermes Discord profile, restrict channels, restart the gateway, and test in one private channel. If Discord uptime, permissions, and gateway restarts are business-critical, compare FlyHermes before owning the deployment yourself.
Use this page as the short implementation checklist for Discord. For why Discord is useful, start with the Discord integration overview; for deeper permission, gateway, and Docker troubleshooting, use the full Discord setup article.
Managed cloud · API costs included · Skill library · Cancel anytime
Before you start:
- ☑Hermes Agent installed and running
- ☑A Discord account with server admin permissions
- ☑Access to discord.com/developers
Steps
- 1
Create the Discord application
Use the Discord Developer Portal to create an application and add a bot user.
- 2
Enable the required intent
Enable Message Content Intent if Hermes must read normal channel messages; keep slash-command-only workflows narrower when possible.
- 3
Invite the bot safely
Generate an OAuth2 invite with bot and applications.commands scopes, then grant only the permissions needed for the test channel.
- 4
Configure the active Hermes profile
Store the bot token in the config or environment for the Hermes profile that runs the Discord gateway.
- 5
Restrict and verify
Limit the bot to one test channel, restart Hermes, then verify that allowed channels respond and blocked channels stay quiet.
Pro Tips
- 💡Start in a private server or hidden staff channel before inviting the bot into a live community.
- 💡Prefer mention-only or slash-command behavior in busy servers.
- 💡Use a dedicated Hermes profile for Discord so team memory and secrets stay isolated.
- 💡After Discord replies in one test channel, use the Hermes WebUI dashboard and gateway status before adding public server channels; use FlyHermes if you do not want to own VPS/Docker uptime.
Troubleshooting
❌ Bot is online but silent
✅ Check Message Content Intent, channel permissions, channel allowlists, mention-only policy, and whether the Discord gateway restarted after config changes.
❌ Slash commands do not appear
✅ Confirm the invite included the applications.commands scope and wait for command registration to propagate.
❌ Bot sees the wrong files or config
✅ Inspect Docker volume mounts and terminal backend settings; use the Docker Discord container troubleshooting guide if the gateway is containerized.