meraGPT

August 22, 2026 · 7 min

Turn your Hermes Agent into a Slack bot

Slack is the third channel people ask about, after Telegram and Discord. It takes a couple more clicks than either because Slack makes you declare scopes up front. The upside is that once it’s wired, your Hermes Agent lives in the place you already spend the day. You @-mention it in a channel or DM it, and it answers with your model, your skills, your memory.

The whole thing runs in Socket Mode, which means Slack opens a connection to your box rather than calling a public webhook. Your box never has to be reachable from the internet. Total time: about twelve minutes.

1. Create the Slack app

Go to api.slack.com/apps. Click Create New App, pick From scratch, give it a name (this is the name your teammates will see), and choose the workspace it belongs to.

2. Turn on Socket Mode

In the left sidebar under Settings, click Socket Mode and flip the toggle on. Slack prompts you to create an app-level token with the connections:write scope. Give it any name, click Generate, and copy the token. It starts with xapp-. Keep the tab open, you need one more token.

3. Add bot scopes and install to the workspace

Under OAuth & Permissions, scroll to Bot Token Scopes and add these four:

Scroll back up and click Install to Workspace, then Allow. Slack drops you back on the same page with a Bot User OAuth Token that starts with xoxb-. Copy it. That’s your second token.

4. Subscribe to the two events

Under Event Subscriptions, turn Enable Events on. Because Socket Mode is already on, there is no Request URL to fill in — Slack greys it out. Open Subscribe to bot events and add:

Save the changes. Slack may ask you to reinstall the app so the new events take effect; if it does, click through it.

5. Paste both tokens into your box

From your meraGPT dashboard, click Open your agent, then CHANNELS in the left sidebar. Find the Slack row and click Configure. The modal wants:

As with Discord, the allowlist is not optional. A bot token with no allowlist would answer every message it can see and bill each one to your key, so the gateway refuses to engage until you name the channels. Click Save & enable. The Slack row flips to Connected and the gateway picks it up on its next restart, usually a few seconds.

6. Invite the bot and talk to it

In the channel you allowlisted, type /invite @your-bot-name. Then @-mention it: “@your-bot what’s on my calendar today?” You get a streaming reply within a second or two. DMs work the same way, no @-mention needed there.

When it doesn’t reply

Open LOGS in the dashboard sidebar and filter to gateway. The usual suspects:

One agent, every channel

Hermes keeps a session per Slack channel and per DM, the same way it does for Discord. Ask it something in #eng today and it remembers yesterday’s #eng; a DM is its own thread. You can see all of them under SESSIONS. The same agent answers in Telegram, Discord, the web chat, and anywhere else you turn on, so a morning brief you set up over Telegram is the same agent you ping in Slack at 3pm.

Before you put it in a shared channel

A meraGPT box is one person’s agent on one person’s key. Drop the bot in a busy team channel and every message it is asked to handle runs through your LLM provider on your bill. The channel allowlist bounds that by room, not by person, so keep it in focused channels rather than a company-wide #general unless you mean to.

Related