Integration
Hermes Agent Discord Bot Setup: Gateway, Intents, Threads
Set up a Hermes Agent Discord bot with Message Content Intent, channel allowlists, thread/forum checks, gateway status, real reply tests, and the managed FlyHermes path.
Quick answer
To set up a Hermes Agent Discord bot, create a Discord application, add a bot, invite it to one private test channel, enable Message Content Intent only when Hermes must read normal channel text, store the token in the active Hermes gateway profile, restart the gateway, and verify one real mention or slash command in the exact channel or thread. Use the Web UI and hermes gateway status as checkpoints, but treat a real Discord reply as the proof. Choose FlyHermes when the business goal is managed Discord/mobile access without maintaining VPS, Docker, provider keys, and gateway restarts. The dashboard helps you inspect gateway/provider state, but a real Discord setup is only proven after a reply lands in the target channel. If you do not want to run the gateway, bot token, server process, and channel uptime yourself, use FlyHermes for the managed path.
Managed cloud · API costs included · No gateway maintenance
Best for
Team support channels and community triage where replies should stay visible to the group
Slash-command workflows with permission boundaries instead of a broad always-listening bot
Threaded debugging and human-agent handoffs in Discord forum channels
Cron, GitHub, CI, Kanban, and gateway alerts delivered to a shared operations room
Teams comparing a self-hosted bot stack against FlyHermes managed cloud channels
Features
- ✓Discord bot setup through the Developer Portal with narrow bot scopes and channel permissions
- ✓Slash commands, app mentions, free-response channels, and thread-aware team workflows
- ✓Message Content Intent guidance so the bot reads messages only when the workflow needs it
- ✓Gateway health checks through hermes gateway status, logs, and the Hermes WebUI dashboard
- ✓Dedicated Hermes profiles for community bots so secrets, tools, and memory stay scoped
- ✓FlyHermes routing for teams that want managed Discord/mobile access without VPS maintenance
- ✓Hermes Discord setup for app mentions, slash commands, threads, and free-response channels
- ✓Message Content Intent and channel allowlist guidance for safer bot reads
- ✓Gateway status checks for Docker, VPS, and hosted deployments
- ✓v0.16 dashboard/admin checks before rebuilding Discord bot permissions
- ✓One-channel Discord smoke test before public server, forum, or support-thread rollout
- ✓Provider-vs-Discord failure split so teams do not rotate bot tokens when credits or rate limits are the real blocker
- ✓Fresh 2026 community evidence: bot invites, platform-scoped tools, gateway restarts, and thread/channel permission issues are recurring support asks
- ✓Weekly conversion update (2026-06-22): position this integration as an always-on channel workflow; if the buyer does not want gateway logs, provider fallbacks, VPS restarts, and dashboard maintenance, route them to FlyHermes.
- ✓Claude Code alternative handoff: use Discord when coding-agent output needs phone/team delivery rather than another terminal tab
- ✓Web UI checkpoint before token churn: verify profile, provider, gateway, cron, and logs before rotating bot credentials
Setup path
- 1Create a Discord application and bot in the Discord Developer Portal.
- 2Choose the smallest permission surface: slash commands/app mentions first, Message Content Intent only when ordinary channel text is needed.
- 3Invite the bot to one test server and one private channel before expanding to public channels or forum threads.
- 4Put the bot token in the active Hermes gateway profile and avoid committing tokens into Docker Compose files or screenshots.
- 5Run hermes gateway setup or configure the Discord platform, then restart the gateway so the token and channel allowlists load.
- 6Verify end to end with hermes gateway status, WebUI gateway status, one Discord mention/slash command, and recent agent logs.
- 7Only after the test channel works, add support threads, cron alerts, GitHub/CI notifications, or community moderation workflows.
Discord setup order
Do not start by dropping the bot into a live server. Build a private test channel, prove one mention or slash command, then expand to threads, forum channels, and community support workflows.
- •Create app and bot in Discord Developer Portal
- •Enable Message Content Intent only when needed
- •Put the token in the active Hermes gateway profile
- •Verify with hermes gateway status and Web UI logs
Discord setup decisions that affect reliability
Discord has more permission surfaces than Telegram: server roles, channel overrides, slash-command scopes, thread behavior, message-content intent, and gateway process state. Keep the first deployment intentionally small, then expand only after one channel works.
- •Start with one test server and one private channel.
- •Prefer slash commands or app mentions when you do not need free-form message reading.
- •Use a dedicated Hermes profile for community bots so memory, skills, env vars, and tool access are scoped.
- •Keep bot tokens in the active profile environment, not in committed compose files.
Copy-paste verification checklist
After adding the bot token and restarting the gateway, verify the live path before inviting the bot into more channels.
- •Run hermes gateway status and confirm Discord is connected.
- •Open the Hermes WebUI dashboard and check gateway/platform health.
- •Send one mention or slash command in the test channel and confirm a reply.
- •Inspect recent agent/gateway logs if Discord receives the message but Hermes does not answer.
- •If a VPS or Docker service is involved, confirm the running process sees the same profile and env file as the CLI smoke test.
One-channel proof before a Discord rollout
The searcher is usually not asking whether Discord can host a chatbot. They need to know whether Hermes will answer safely in their server. Keep the first proof tiny: one bot, one private channel, one active Hermes profile, one provider route, and one real mention or slash command. Only then add support forums, public channels, cron alerts, or team workflows.
- •Create the app and bot in the Discord Developer Portal, then invite it to one private test channel.
- •Use app mentions or slash commands first; enable Message Content Intent only when normal channel text must be read.
- •Put the token and allowed channel IDs in the same Hermes profile that runs the gateway.
- •Restart the gateway and prove a real reply in Discord before expanding permissions.
Discord verification matrix
A green process status is not the same as a working Discord agent. Verify each layer separately so setup work does not turn into random token rotation.
- •Provider layer: run one CLI turn from the same profile and fix credits, API keys, fallback routing, or rate limits first.
- •Gateway layer: run
hermes gateway status, inspect Web UI gateway/platform health, and restart after config changes. - •Discord layer: test app mention/slash command, Message Content Intent, channel allowlist, role permissions, and thread/forum permissions.
- •Production proof: send one message in the exact channel, thread, or forum post that will receive real work.
Managed Discord agent path
Self-hosting is powerful when you want full control over profiles, tools, secrets, gateway logs, Docker, and VPS uptime. FlyHermes is the cleaner path when the business outcome is a reliable Discord or mobile agent and the team does not want to operate the gateway stack.
- •Use self-hosted Hermes when runtime control and local tool access matter most.
- •Use FlyHermes when uptime, connected channels, browser/mobile access, and provider operations matter more than maintaining servers.
- •Use the pricing page as the decision point after one local proof-of-concept works.
Message Content Intent and channel allowlists
A Discord bot that 'sees nothing' is usually missing the Message Content Intent — enable it in the Developer Portal, then scope the bot to specific channels with an allowlist so it doesn't react everywhere. Thread support and per-channel control are what make Discord the community's preferred way to run a shared, always-on agent.
Discord as a team agent surface
Discord is frequently described as the best way for a group to work with a Hermes agent — multiple people in one channel, threads for separate tasks, and the agent always present. That always-present part is the catch: the gateway must run continuously. Teams that don't want to babysit a server run the Discord gateway on a managed host so it stays online through restarts and updates.
Common setup issues
- Bot online but not responding: check Message Content Intent, app mention policy, channel allowlists, server/channel permissions, and whether the gateway was restarted after config changes.
- Works locally but fails in Docker/VPS: verify the container or service has the same Discord token, profile path, .env values, and working directory as your local smoke test.
- Thread or forum replies fail: test one normal channel first, then one private thread, then inspect gateway logs for message_thread_id/thread permission errors.
- Unauthorized users trigger reactions or threads: narrow role/channel permissions and split the Discord bot into a dedicated Hermes profile with fewer tools.
- After a Hermes update, fully restart the gateway process instead of only resetting the chat session; stale gateway processes can keep old adapter code in memory.
- Dashboard says connected but Discord is silent: use Web UI as a checkpoint, then verify Message Content Intent, app mention policy, channel/thread permissions, allowlists, stale gateway process, and one real message in the target channel.
- Dashboard says connected but Discord is silent: Web UI only proves one checkpoint. Send a real message in the exact Discord channel/thread, then check Message Content Intent, app mention policy, channel allowlists, profile path, provider credits, and stale gateway process state before regenerating the bot token.
- Use the Hermes dashboard to inspect gateway logs and provider state, then verify one real Discord send/reply in the exact target channel before calling the integration healthy.
- Choose FlyHermes when the blocker is always-on channel uptime, provider plumbing, or server restarts rather than a one-time bot-token setup.
Keep building the workflow
Hermes Agent Discord setup guide
Full Developer Portal, bot token, intent, gateway, and troubleshooting sequence.
Connect Discord to Hermes checklist
Short setup checklist for the Discord gateway path.
Hermes WebUI dashboard
Use WebUI to verify gateway and platform health after setup.
FlyHermes managed cloud pricing
Choose the managed path when you do not want to operate Discord gateway infrastructure.
Hermes Docker Compose
Self-host long-running gateway services with Docker when you want full control.
FAQ
How do I add Hermes Agent to Discord?
Create a Discord app and bot, choose narrow scopes, enable Message Content Intent only if you need normal channel text, invite the bot to one test channel, put the token in the active Hermes gateway profile, restart the gateway, then verify one mention or slash command.
Why is my Hermes Discord bot online but not responding?
Check Message Content Intent, channel permissions, app mention policy, channel allowlists, gateway restart state, and the active Hermes profile. If it runs in Docker or on a VPS, confirm the service can read the same token and config as your local test.
Does Hermes Agent need Discord administrator permissions?
Usually no. Start with the smallest permission set that allows the target workflow: app mentions, slash commands, reading selected channels, and posting replies. Expand only after the test channel works.
Can Hermes Agent run in Discord threads and forum channels?
Yes, but thread behavior depends on bot permissions and gateway configuration. Test a normal channel first, then a private thread, before using the bot in a live community forum.
Should I self-host the Discord bot or use FlyHermes?
Self-host when you want full control over profiles, tools, tokens, VPS, Docker, logs, and restarts. Use FlyHermes when the business need is managed Discord/mobile access without operating the gateway stack yourself.
How do I set up Hermes Agent Discord?
Create a Discord app and bot, invite it to a private test channel with narrow permissions, configure the token in Hermes, restart the gateway, then verify one mention or slash command before expanding access.
Why is Hermes Discord online but not replying?
Check Message Content Intent, channel permissions, app mention policy, allowlists, the active Hermes profile, and gateway logs. In Docker or VPS setups, also confirm the container can read the same config and token.
What should I test before inviting Hermes into a real Discord server?
Test one CLI turn from the same profile, restart the gateway, check Web UI/gateway status, then send one mention or slash command in a private Discord channel. After that works, test the exact thread or forum channel that will receive production traffic.
How does Discord fit a Claude Code alternative workflow?
Discord is the delivery layer when the agent work should reach a phone, team channel, support thread, or scheduled report instead of staying inside a terminal. Use Hermes Web UI to inspect gateway health, then verify a real Discord reply.