Blog Article

How I Have My Hermes and OpenClaw AI Agents Working Together

A walkthrough of bridging Hermes and OpenClaw agents through a shared Discord layer, letting executive-assistant agents Neo and Muddy wire up new bots like Warren

Two agent frameworks. Two different platforms. One shared Discord server doing the connective work. That is the entire trick.

In this build, I walk through how I get my Hermes agents (Neo, Cypher) talking to my OpenClaw agents (Muddy, Warren) without writing a single line of custom integration code. The glue is Discord, and the wiring is done by the executive assistant agents I already trust on each side.

The Approach: Let Your Agents Configure Themselves

The simple pattern: create a Discord bot per agent, create a shared channel, connect each bot, set the rules, rinse and repeat.

Instead of doing this manually, I prompt my existing executive assistants to mirror the setup pattern they already use. Neo lives on Hermes. Muddy lives on OpenClaw. They have been coordinating in a shared executive assistant chat since April 25th, so the recipe is already proven. New agents just inherit it.

The prompt I sent Muddy was short:

> "It's time we set up Warren with his own Discord bot, plus give him shared comms and growth with our Hermes agent. Like we did with you and Neo."

Muddy came back with: "I'm going to mirror Muddy and Neo pattern, verify the exact config surface, then apply it cleanly without guessing." He inspected the existing config, confirmed there was no Warren Discord token yet, and produced the step-by-step. This is why we ask our agents for instructions.

Same flow on the Hermes side with Neo for Cypher, my growth agent. Neo discovered Cypher already had a workspace, profile, and Discord config, but was not running as his own bot yet. Step-by-step came back the same way.

The Discord Bot Recipe

Whether you are setting up Warren, Cypher, or any future agent, the steps are identical:

  • Go to the Discord Developer Portal and create a New Application. Name it after the agent.
  • Assign the application to the correct team and confirm you are human.
  • In the Bot tab, toggle on two privileged intents: Server Members Intent and Message Content Intent. Without these, the bot cannot actually read or respond to messages.
  • Set the bot's permissions: Send Messages, Create Public Threads, Create Private Threads, Send Messages in Threads, Add Reactions, Read Message History, View Channels.
  • In OAuth2, open the URL Generator, select scopes bot and applications.commands, then check the same permissions again.
  • Copy the generated OAuth URL, paste it into your browser, pick the target server (mine is Clearmud Ops), and authorize.
  • Assign a role (like "Hermes") to scope which channels the new bot can see.

One bot per agent, not one bot per platform. That keeps every message and reaction attributable to the right agent.

Platform Quirks Worth Knowing

Hermes leans on threads. OpenClaw does not natively use them. The fix is to give both sides the same permission set so they can operate at parity in the shared channel.

Discord itself can also misbehave. Fun fact: I had to wait about an hour and a half to record this video because Discord had an API outage. By the time I was recording, the bots were back online but the typing indicators ("Neo is thinking") were not firing. That is a Discord glitch, not your wiring. Expect that kind of thing and do not assume the bridge is broken when the platform itself is degraded.

Test It With Real Work

While Warren and Cypher were being configured in the background, I gave Neo and Muddy a real task in their shared chat: build a landing page for Clearmud Labs at labs.clearmud.ai, pull from the clearmud/clearmud-labs GitHub repo, use the Clearmud front-end design skills, QA each other, and ping me when one is ready for my eyes.

That is the real value of this setup. Once two agents can see each other in a shared room, you can delegate multi-agent projects conversationally. They handle the back and forth, they check each other's work, and they come back to you only when they need a human in the loop.

The Gist

Create the bots. Create the channel. Connect them. Set roles. Let your assistant agents do the heavy lifting on configuration. The rest is just rinse and repeat for every new teammate you bring online.

Watch the full walkthrough: https://www.youtube.com/watch?v=ziSeVy5p9ck

Watch the full walkthrough on YouTube.

Watch on YouTube