Hermes just picked up one of the most useful integrations it has had in a while, and the phrase to know is hermes agent buzz — your Hermes agent running inside Buzz, working directly in channels alongside your team. I went through the whole thing hands-on, all three connection routes included — here is the plain-English walkthrough of what it is, how to wire it up, and why it is worth twenty minutes.
The short version: Buzz is like an AI-powered Slack. Hermes is your agent stack. Connect the two and every bit of your Hermes setup — config, credentials, memory and skills — lives inside a chat interface your whole team can actually use.
What is Buzz?
Buzz comes from Jack Dorsey and you can get it at buzz.xyz. Think of it as an AI-powered Slack: channels, threads, DMs, the layout everyone already understands. The difference is that your AI agents work directly inside those channels as members of the workspace, rather than sitting in a separate tab you keep switching to.
You can invite humans in too, so it is a genuine team space rather than an agent playground. And you can plug in different agent providers — Claude, Codex, and now Hermes.
Why bother with a hermes agent buzz setup?
Fair question, and it is the first one I got asked: if you already run Hermes, why add Buzz on top?
My honest answer is that Buzz is simply a lot more intuitive and easier to use. Hermes is powerful, but it is an agent runtime. Buzz is a chat app your team already knows how to use on day one.
The important part is that you give up nothing to get that. Hermes runs inside your Agent OS — your configuration, credentials, memory and skills — and connecting it to Buzz keeps all of that intact. Buzz just becomes the friendly front door for a team: your stack stays where it is, and everyone else gets a doorway in that does not require a terminal.
📺 Watch: Hermes Agent + Buzz is INSANE!
The three ways to connect Hermes to Buzz
There is not one path here, there are three, and they suit different setups. Here is how they compare.
| Connection method | What it actually does | Best when |
|---|---|---|
| Buzz Desktop auto-discovery | Buzz Desktop finds your Hermes install on its own — no manual wiring | You want the fastest route and Hermes is already installed locally |
| Relay bridge | Gives Hermes a hosted identity in your channels, while Buzz's own harness owns the transport | You want Hermes present in a hosted community without running the transport layer yourself |
| Hermes Gateway | A bundled Buzz platform plugin that makes Buzz a full external platform: channels, DMs, threads, reactions and scheduled task delivery | You want the deepest integration and the complete feature set |
1. Buzz Desktop auto-discovery
The simplest of the three. Install Buzz Desktop, and it goes looking for your Hermes install by itself. If it finds it, you are effectively done — no config files, no relay URL, nothing to paste.
2. The relay bridge
The relay bridge gives Hermes a hosted identity inside your channels. Hermes shows up as a proper participant, but Buzz's own harness handles the transport. That split matters: you get Hermes in the room without owning the plumbing.
3. The Hermes Gateway
This is the deep one, and the route I walked through. The Hermes Gateway is a bundled Buzz platform plugin, so Buzz is treated as a full external platform rather than a chat window bolted on the side. You get channels, DMs, threads, reactions and scheduled task delivery.
📺 Watch: Jack Dorsey's Buzz DESTROYS Hermes Agent?
Setting it up step by step
Here is the exact order I ran it in. Do not skip the first two — most problems come from getting ahead of yourself.
- Download Buzz from buzz.xyz and install it.
- Update Hermes first. The Buzz integration is new, so an old build simply will not have it.
- Make sure Hermes ACP is set up. If you are not technical, do not grind through this by hand — get Claude or another agent to set it up for you. That is genuinely the intended path now, not a cop-out.
- If Hermes is not auto-discovered, open settings and use add runtimes to install more agents. That is where Hermes appears if Buzz did not spot it on its own.
- Run hermes gateway setup in your terminal and select Buzz from the list of platforms.
- Give it the relay URL. This is your community URL, and you will find it in your hosted community settings.
- Leave the channel UUIDs empty. Blank means Hermes joins every channel, which is almost always what you want to start with. Fill them in later if you need to keep the agent penned into specific rooms.
- Allow all community members to talk to the agent, then hit done.
- Restart the gateway so it picks up the changes. Skip this and you will sit there wondering why nothing happened.
Make Hermes the default agent in Buzz
Once the gateway is live, hop back into Buzz and finish the job on that side. Go to settings, then agents, then agent defaults. Select your Hermes agent and save the defaults.
Now Hermes is the default provider. Anyone typing in a channel is talking to your Hermes setup without needing to know that is what they are doing.
Switching the model — including free ones
With Hermes as the provider, you can change the model behind it. That includes running a free API or a free model, such as Ling 3.0, sitting behind Buzz. For a team workspace where a lot of the traffic is quick questions and small jobs, that is a genuinely useful lever to have.
Which model you run behind Buzz depends on the work. In my own hands-on testing over on Goldie Bench, the gap between models widens sharply once tasks get multi-step, so my personal rule is a free model for chatty, low-stakes channel traffic and something stronger for anything touching real deliverables. That is my read from testing, not a universal truth — run your own jobs through it first.
📺 Watch: Hermes Agent: New Voice Activation Update is INSANE!
Now go the other way: control Buzz from Hermes
Here is the part I did not expect to enjoy as much as I did. The connection is not one-directional. You can also ask Hermes to control Buzz locally, as an app.
I asked Hermes to send a test message in Buzz, and it wrote one and sent it. No integration wizard, no extra plugin — just Hermes driving the app on the machine.
Controlling Buzz from your phone
This is where it gets properly practical. Hermes can connect to Telegram or other messaging platforms. So if Hermes can drive Buzz locally and you can reach Hermes from Telegram, you can effectively run Buzz from your phone.
Message Hermes on Telegram, Hermes acts inside Buzz, your team sees the result in the channel. You never opened a laptop.
If you want Hermes and Buzz set up to make you money, check out the AI Profit Boardroom — the full Agent OS build and the Buzz masterclass are inside, with the community and workflows to turn that setup into paid work. → Get my Hermes and Buzz setup
Hermes agent Buzz FAQ
Do I need all three connection methods?
No. Pick the one that matches your setup. Auto-discovery is fastest if Hermes is already on the machine, the relay bridge suits a hosted community, and the Hermes Gateway gives you the full platform integration.
What if Buzz does not find my Hermes install?
Go to settings and use add runtimes to install more agents. That is the manual fallback when auto-discovery comes up empty. Also double-check you updated Hermes first.
Do I have to be technical to set up Hermes ACP?
Not really. If the ACP step is beyond you, get Claude or another agent to set it up for you. That is the route I would point most people at.
Where do I find the relay URL?
It is your community URL, and it lives in your hosted community settings. Paste that into the gateway setup when it asks.
Should I fill in the channel UUIDs?
Leave them empty to start. Blank means Hermes joins all channels. Add specific UUIDs later only if you want to restrict which rooms the agent operates in.
Why use Buzz if I already have Hermes?
Because Buzz is simply a lot more intuitive and easier to use. You keep your entire Hermes agentic setup — config, credentials, memory and skills — and you get a chat interface your team can pick up without training.
Nothing happened after setup. What did I miss?
Almost certainly the restart — the gateway needs restarting to pick up your changes. After that, check Hermes is set as the default provider under settings, agents, agent defaults.
The Bottom Line
The hermes agent buzz integration is a genuinely good bit of engineering because it does not ask you to rebuild anything. Three routes in — Buzz Desktop auto-discovery, the relay bridge, or the Hermes Gateway plugin — and whichever you pick, your Hermes config, credentials, memory and skills come with you.
Update Hermes, sort out ACP, run hermes gateway setup, point it at your relay URL, leave the channel UUIDs blank, restart the gateway, then set Hermes as the default agent in Buzz. From there you can swap in a free model, drive Buzz from Hermes locally, and reach the whole thing from your phone through Telegram.
Your Agent OS keeps doing the heavy lifting underneath. Buzz just makes it something a team can walk up to and use.
