agentos.guide › blog

Hermes Agent Discord: Set Up, Lock Down And Run A Server Bot In Your Agent OS With 5 Copy-Paste Prompts

By Julian Goldie · 11 November 2026 · agentos.guide

Hermes Agent Discord inside your Agent OS means your agent sets up, locks down and runs its own Discord bot, and you mostly just talk to it.

You still do the Developer Portal clicks yourself, because only you can log into your Discord account.

After that, the five prompts below do the rest: an audit, a staff-only lockdown, a help channel, a daily summary and voice.

Fancy a hand planning which channels to automate? Book a free SEO strategy session with my team.

Quick Start: The Four Things You Do By Hand

Everything here comes from the Hermes Discord guide.

1. In the Discord Developer Portal, create a New Application, open Bot, and switch on Message Content Intent and Server Members Intent. Save.
2. Click Reset Token and copy the token. Discord only shows it once.
3. Run the wizard and paste the token when it asks.
4. Open the invite link the wizard prints, choose your server and authorise it. You need Manage Server on that server.

hermes gateway setup
hermes gateway install

The wizard checks the token with Discord, warns you if Message Content is still off, and offers to allowlist you as the owner.

The second command keeps the gateway running as a service, so the bot stays online after you close the terminal.

Skip the intent and Discord refuses the connection; the docs call it the most common reason a Discord bot never works.

How The Bot Behaves Before You Change Anything

• It answers every DM, and each DM is its own session.
• In server channels it only answers when someone @mentions it, then carries on in a new thread.
• Two colleagues in one channel get two separate conversations.
• It stays quiet when a message tags somebody else.
• It can't ping @everyone, @here or roles.
• It denies everyone who isn't on an allowlist, a role list or an allowed channel.

Those defaults are sensible, so the prompts below only change what a small business actually needs changed.

Prompt 1: Audit The Setup Before Anyone Else Joins

Check my Hermes Discord setup before I invite anyone.
1. Run hermes gateway status and read ~/.hermes/logs/gateway.log.
2. Tell me if Discord connected, or if the log mentions privileged
   Gateway Intents (that means Message Content Intent is off).
3. List which of these are set in ~/.hermes/.env, without printing
   any token: DISCORD_BOT_TOKEN, DISCORD_ALLOWED_USERS,
   DISCORD_ALLOWED_ROLES, DISCORD_ALLOWED_CHANNELS.
4. If no access policy is set, stop and tell me. Do not set
   DISCORD_ALLOW_ALL_USERS.

This catches the two failures the docs list most: an intent left off, and a bot with no access policy.

The second one looks like a broken bot, because it connects and then ignores everyone, but it's the safe default at work.

Telling the agent not to print tokens matters, because whoever holds the token controls the bot.

Prompt 2: Make It Staff-Only With Roles

Lock my Discord bot down to staff.
- Add role ID STAFF_ROLE_ID to DISCORD_ALLOWED_ROLES.
- Set DISCORD_ALLOWED_CHANNELS to: TEAM_CHANNEL_ID, HELP_CHANNEL_ID.
- Add ANNOUNCEMENTS_CHANNEL_ID to DISCORD_IGNORED_CHANNELS.
- Under gateway.platforms.discord.extra, make my user ID the only
  allow_admin_from entry, and set user_allowed_commands to status
  and model.
- Show me the diff, then run hermes gateway restart.

Roles beat user lists for a team that changes.

Give a new starter the staff role and they're in straight away, with no config edit or restart.

The admin split means your staff can chat freely, but only you can run every slash command; /help and /whoami always stay available.

Fill in the real IDs by switching on Developer Mode under Settings → Advanced and right-clicking a role or channel.

🔥 Want the full Agent OS set up for Discord, not just one bot?

Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running Hermes on their own servers.

→ Join the AI Profit Boardroom

Prompt 3: A Help Channel That Needs No Tag

Turn HELP_CHANNEL_ID into a no-tag help channel.
- Add it to discord.free_response_channels in config.yaml.
- Add a discord.channel_prompts entry for it:
  "You answer questions from our team about bookings, opening
  hours and our services list. If you are not sure, say so
  and tag the manager. Never post to any other channel."
- Keep group_sessions_per_user: true.
- Restart the gateway and tell me how to test it.

Free-response channels answer inline, without a thread, so they feel like a normal chat.

The channel prompt is applied on every turn but isn't saved into history, so editing it changes the very next reply.

A hair salon could use this for its team: a stylist asks "is Thursday at 2 still free?" and Hermes answers from whatever booking file you give it access to.

An accountant's office could point the same channel at its internal deadlines sheet instead.

Prompt 4: A Daily Summary Posted To A Home Channel

Set up a weekday summary in Discord.
- Run /sethome in TEAM_CHANNEL_ID (or set DISCORD_HOME_CHANNEL).
- Create a cron job, paused, for 5pm Monday to Friday:
  "Summarise today's job notes from the team channel into
  five bullets: done, waiting on parts, follow-ups.
  Draft only: this is for the owner, nothing goes to customers."
- Deliver it to the Discord home channel.
- Run it once by hand so I can read it before you resume it.

The home channel is where Hermes posts proactive output such as cron results and reminders.

Starting the job paused and running it once by hand means the first summary you see is one you asked for.

Here's how a plumbing firm might use it.

1. Plumbers leave voice messages in the team channel after each job, and Hermes transcribes them.
2. At 5pm the job reads the day's notes and writes five bullets.
3. The owner reads it in the home channel and decides what to chase tomorrow.

Writing "draft only" into the job keeps anything customer-facing in human hands.

Prompt 5: Voice Messages And Voice Channels

Get voice ready in our Discord.
- Check the bot was invited with the Full permission set
  (309240908864, adds Connect and Speak). If not, give me
  a fresh invite link.
- Confirm which speech-to-text provider is configured; prefer
  local faster-whisper.
- Tell me the commands to make you join and leave a voice
  channel, and set voice_channel_inactivity_timeout_seconds
  to 300.

Voice messages are transcribed automatically; local faster-whisper needs no API key.

Hermes can also join a voice channel, listen and answer out loud, which is why the Full permission set exists.

By default it leaves after 300 idle seconds, and the /voice command handles join, leave and TTS replies.

More options live in the Hermes voice mode docs.

One more pattern worth stealing: a small marketing agency can give every client channel its own channel prompt, so the same bot writes in a different voice in each room.

Ask your agent to add those entries one client at a time and to read each prompt back to you before restarting.

If a client channel should never get answers at all, list it in the ignored channels instead, because that setting wins over every other channel rule.

A Weekly Routine For A Small Team Server

For a fuller support setup built on the same pieces, see Hermes Agent for customer support in your Agent OS.

Rules Your Agent Should Never Break On Discord

• No unprompted DMs and no bulk messages to members, whatever the task says.
• Never set DISCORD_ALLOW_ALL_USERS or GATEWAY_ALLOW_ALL_USERS on a server where strangers can post.
• Anything going to customers is a draft for a human to send.
• Keep the ping block for @everyone and roles switched on.
• Remember that anyone authorised gets the agent's tools, so keep the allowlist short.

🔥 Get a free second opinion on your rollout

Book a free SEO strategy session and my team will look at where Hermes fits in your business before you open it up to anyone.

→ Book a free call with my team

Fixes When Something Goes Quiet

Paste the symptom into your agent and ask it to check the gateway log first; most of these show up there by name.

• Offline: Message Content Intent is off, the gateway isn't running, or the token is stale.
• Online but silent: no access policy, and the log says "No Discord access policy configured".
• Silent for one person: their user ID or role isn't allowed.
• Blind in one channel: the bot's role lacks View Channel and Read Message History there.
• Error 50001 on /thread: the parent channel or category has an override that denies thread permissions.

If you're on Hermes Cloud with Team Gateway switched on, Discord reaches your agent through a shared Hermes bot rather than your own, so these portal fixes apply only to a bot you run yourself.

Stuck after all that? Book a free call with my team and we'll look at it with you.

The latest v0.23.1 patch notes list nothing new for Discord, and since v0.23.0 one gateway per machine owns every session, so your desktop app and your Discord bot share one history.

The source code is on GitHub if you want to read the adapter yourself.

Ready to run it with the rest of your stack? Join the AI Profit Boardroom and get the Agent OS installed.

FAQ

Can my agent create the Discord bot for me?

Not entirely. You create the application, switch on the intents and copy the token in the Discord Developer Portal yourself; the agent can handle the config, access rules and jobs after that.

Why use roles instead of user IDs?

Anyone holding an allowed role is authorised straight away, so staff changes need no config edit or gateway restart.

Where do scheduled summaries appear?

In the home channel, which you set with /sethome or DISCORD_HOME_CHANNEL.

Will the help channel mix up different people's questions?

No. group_sessions_per_user is on by default, so each person has their own session even in a shared channel.

Does the bot read every channel?

No. It only answers in server channels when tagged, unless a channel is listed as free-response, and you can restrict it further with allowed and ignored channel lists.

Final word on Hermes Agent Discord

Do the four portal clicks, paste Prompt 1 into your agent, and if you want the whole system ready to go, join the AI Profit Boardroom and run Hermes Agent Discord from your Agent OS.

Related guides on agentos.guide

→ Hermes Agent Slack: Run Your Agent In Slack From Your Agent OS

→ Hermes Agent Telegram: Run It From Your Agent OS

→ Hermes Agent WhatsApp: Five Prompts To Run In Your Agent OS

→ Hermes Agent For Business: Start With One Job, Then Grow It With Five Copy-Paste Prompts In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide