Hermes Agent in Buzz einrichten und Multi-Agenten vernetzen

VideoTonbi's AI GarageAnleitung

Ein Video-Tutorial zeigt die Integration von Nous Researchs Hermes Agent in den kollaborativen Workspace Buzz über das native Gateway. Neben der Lösung des häufigen Fehlers fehlender CLI-Binaries demonstriert der Entwickler, wie mehrere Agents über verschiedene Rechner hinweg zusammenarbeiten und Fakten gegenprüfen.
Beim Abspielen wird YouTube (youtube-nocookie.com) geladen.

Das Wichtigste

  1. Nous Research bietet eine native Integration für Hermes Agent in Buzz; der Autor empfiehlt das native Gateway gegenüber der Desktop-ACP-Laufzeit, da es Cronjobs, Reaktionen, Bildverarbeitung und Session-Memory vollständig unterstützt.
  2. Zentrales Problem beim Setup: Das Buzz CLI muss zwingend im System-PATH liegen. Fehlt es, reagiert der Agent zwar auf Nachrichten mit Emojis, kann jedoch keine Textantworten zurücksenden.
  3. Der Einrichtungsprozess erfordert das Erstellen eines Agents in Buzz, das Kopieren des Nostr-Private-Keys sowie das Ausführen von 'hermes gateway setup' mit Angabe der Relay-Community-URL und Pubkeys.
  4. Über ein Open-Source-Skill-Repository (tonbistudio/buzz-skills) wird die Installation der CLI-Binaries und die Konfiguration der Zugangsdaten über ein Skript direkt durch den Agenten automatisiert.
  5. Demonstration von persistentem Gedächtnis: Ein auf einem VPS betriebener Agent greift in Buzz nahtlos auf den Gesprächsverlauf aus vorherigen TUI-Sitzungen zu.
  6. Praxis-Demo mit drei Agents auf unterschiedlicher Hardware (lokaler PC, DGX Spark, VPS), die in einem gemeinsamen Thread Updates recherchieren und Korrekturen abstimmen.

Warum das relevant ist

Multi-Agenten-Systeme scheitern in der Praxis oft an fragmentierten Umgebungen und fehlenden Kommunikationsschnittstellen. Die Kombination aus Buzz und dem Nostr-gestützten Gateway von Hermes Agent demonstriert, wie dezentral verteilte LLM-Instanzen auf unterschiedlicher Hardware in einem gemeinsamen Workspace zusammenarbeiten können.

Einordnung

Der Workflow verdeutlicht die noch unfertige Usability moderner Agenten-Plattformen: Fehlermeldungen in Buzz leiten Entwickler oft in die Irre, wenn elementare Abhängigkeiten wie die CLI fehlen. Die Lösung, dem Agenten eigene Einrichtungs-Skills bereitzustellen, zeigt jedoch das wachsende Potenzial selbstkonfigurierender Entwickler-Tools. Für verteilte Teams bietet dieser Ansatz eine flexible Alternative zu zentralisierten Multi-Agent-Frameworks.

Transkript

Vollständiges Transkript anzeigen (2.518 Wörter)
I'm in Buzz, and I'm working with my multi-agent team using Claude models, using OpenAI models, as well as some of my Hermes agents. And I'm in my private group here. You could see I'm asking questions to my agents. Um, I asked for their opinions about how to make pull requests on a project uh from separate machines. Bulls answers the question. And this is my Hermes agent on my PC. I get a follow-up from Hibana, who's also a Hermes agent but on my DJX Spark that I usually SSH into. And then I get kind of a confirmation from Sonnet, the Claude agent that is on my PC. So, now I have multiple agents working together on my project getting their opinions, getting their work, as we work on projects through a shared project uh folder, a shared repo that we manage together. So, a lot of this wasn't possible uh last week when I put out my beginner's guide to Buzz. So, in this video, I'm going to show you how number one to set up Hermes agent in Buzz. I'm going to introduce a few useful skills that I think will help you make the process a lot smoother. I'm going to show you how you can get them to work together like this. And then I'm going to actually show you how you can get them to work together on a shared repo, so that all of your different agents on different machines can work together on the same project. So, let's get started. And if you run agents yourself and want access to the LM Wikis that I use myself for these videos to do research and actually create them, uh check out my project agentwikis.com. I provide all of these wikis for free on a variety of different topics, and you could also sign up for a pro account for $9.99 a month that will give you access to supersized extra-large wikis that'll give you more pages and more detail on each of the subjects. Now back to the video. Okay, so as you can see, I have a couple agents already running um through Hermes on my Buzz. So, News Research announced the integration with Bugs Buzz through Hermes agent and you can check this on their docs page. Um, there's a couple different ways to do it. Um, you could do it in the desktop runtime itself, and you should be able to see if you go into your settings here, um if you go down to agents, you should be able to see now. Remember last week there was only like these four options. Now, there's a bunch of them, Grok build, Hermes agent, Kimi Code, OpenCode. So, these are all ready to go. Um, so there is a way to do it just through the desktop app itself. And you need to use an ACP uh for this. I've had a little bit of difficulty getting this to to work and I've actually had better success with the number three option, um which is the native gateway platform. So, that is my recommendation. And you can see they recommend it for a full Hermes agent here. And this is familiar if you've been using Hermes agent and you have it set up on Telegram or Discord or something. You'll be familiar with the gateway anyway. Um and it does give you full functionality. Like, it'll give you crondelivery, um everything else like this, images, reactions with Hermes' own approvals, memory and session management intact, which I think is important because you want that as well. Uh so, let me walk you through this. And kind of the tricky thing and something that a lot of people get tripped up on, including myself, um these prerequisites are very important. You need the Buzz CLI binary on your path um in order for this to work. If you don't have that set up, you can get your agent hooked up to it. You can message it, it'll react to you, but it'll never actually respond to you. If you need help with this, um this is my GitHub, tonbistudio/buzz-skills. I'll be putting in more skills by the time you see this probably. Um but this one, Hermes in Buzz, is the skill that helps you set up exactly the CLI and get everything running here. It's not super intuitive, right? This isn't anything. It's just a guide, basically, for your agent. But it's not super automatic or super intuitive for the agents to get a set up. So, that's why I created this, this skill, um that will tell them exactly when to use. Like, the errors that they may run into, security rules, um and the how you would do it. Because it's a little bit tricky. So, I think this skill is is useful, that'll tell them exactly when to use. Like, the errors that they may run into, security rules, um and the how you would do it. Because it's a little bit tricky. So, I think this skill is is useful. So, I have two agents already set up. Um but I want to add the one that is currently on my VPS, that you know as Admiral. And I think what you need to do here is you need to create an agent first. So, let's create an agent. Uh let's call it Admiral. I'll put his picture in later. You are Admiral, a Hermes agent living on my VPS. So, you can just do this harness as Hermes agent and the default, um and then create the agent. So, this will give you a private key here, and this is very important. Um this is what you're going to have to use when you set up the the gateway. So, you're going to want to save this. Okay, so we see Admiral. The green here says it's running, but it's not actually running right now. But I respond to it, it won't do anything. You're going to want to update your Hermes agent if you haven't done it yet. As you can do Hermes gateway setup. And this will open up um this the gateway setup wizard. It'll open up which messaging platform you want to use. And you can see, where is Buzz? Right here. So, let's configure Buzz. So, the relay URL is going to be your community. So, in my case, I have a private community. Uh it's very private. It's just me. Copy community URL here. And then the nostr private key. So, this is the key that I showed you before um although it was blanked out. But this is the one you should be saving. And this is what you're going to connect. And obviously, the agent you create needs to be inside this community for any of this to work. Um so this, I'll just do blank home channel. Blank. Allow all community members to talk to the agent? Yes. So you can restrict control here. Um see if I do no. Allowed users. So comma-separated npubs or hex pubkeys, empty to deny everyone. So, this is your pubkeys, which if you go to settings, right? This'll have it your identity. So, your public key is going to be this. And this is okay to show. It's a public key. Do not show your private key, though. If you do it, they'll have access to your account. So, think of it like um a crypto wallet. If you have one of those, you have a private key right and you have a public key, which is just the address that everyone can see and it's on chain. There we go. All done. Restart the gateway. Sure. So, this connects the gateway to the agent in here, um to Admiral. But it's not done yet, because what you need is the Buzz CLI, which I showed you before in that repo. So, even though the gateway is restarted here, let me show you. This isn't going to work. Um. Let me just DM him. So, you'll get a response, right, with the eyes. So, there is some connection here. And if you click over here on view activity, you'll be able to see. But he's never going to actually be able to respond to me. Because he doesn't have the CLI. You can even see the thinking, right? He's preparing to reply. You can see the tool calls. But see, I couldn't deliver the reply. Um, and it says sometimes it'll give different error. This one says, Buzz rejected the send because the agent is not a member of the DM channel, which isn't true. The real issue is the CLI, like I was saying before. Um, sometimes the errors aren't exactly right. Because you can see the channels he is allowed in the DMs. So, what we need to do is, I'm just going to go into Hermes chat here. Um, there we go. So, this is on Admiral, right. I'm just in the TUI. And I'm just going to say, I want to set up Buzz integration for this agent, please check. This is the skill that I made, Hermes in Buzz, to set up the Buzz CLI. I've already set up the agent in Buzz and the messaging gateway. So, it'll ask for your explicit approval here um with the Buzz CLI setup. And you can see it's running this Python script update Buzz credentials. So, this is important as well. Um, this is part of there's two kind of helper scripts here in the in the skill. So, this is um a way to update your credentials in Buzz. Just kind of a helper script for the agent to do it. 'Cause this needs to be done as well, not just the CLI. And you can see it's running this Python script, update Buzz credentials. So, this is important as well. Um, this is part of there's two kind of helper scripts here in the in the skill. So, this is um a way to update your credentials in Buzz. Just kind of a helper script for the agent to do it. 'Cause this needs to be done as well, not just the CLI. So, the Buzz CLI installation is complete. So, the next is to configure the the path for the CLI, and then restart the gateway, and then it should be connected. Okay, so it should be successfully connected. There's a stage where you need to put in your own private key, which I obviously didn't show. But, um, that's part of the guide. It'll show you where you need to put that. So, everything should be connected here. Go to Admiral. Let's restart him, and let's go to the DMs here. Hello. No home channel set for Buzz. Um but you could set the home channel like you would for Telegram or something like that. Oh, we got a response. Nice. There we go. Hello, Admiral, here. How can I help? Um and just to show you, I asked, uh "Can you tell me the last topic we talked about?" Uh at first it didn't respond so I I said hello. That was confused but then um it did respond to me. It said your last topic was setting up the Buzz CLI integration for this Hermes agent. Uh which is true. You just saw me in the TUI working on the Buzz CLI integration. So you can see how it has the memories, it has access to previous sessions, even on different platforms like you would have with Telegram or whatever, as long as it's the same agent, right? Um, there's some quirky stuff like this, where because it doesn't have the full tool call where you you know the agent is actually working, sometimes it just goes silent like this. Uh but it is working. So there we go. We have Admiral set up. So, we now have three agents on three different machines: Admiral on my VPS, Hibana on my Spark, Bulls on my local PC. So now, let's have them work together a little bit. So, is it Hibana, can you research recent updates to Buzz, and then report them to Bulls? Ask him to double check the new updates. And you can see Hibana responds here. Very long list of the latest updates. And you can see he is uh responding to Bulls, like I asked. So, these are the recent updates. And he asked Bulls to double-check them for me. So, now you can see Bulls is thinking. He's probably going to double-check them for me. And once again, these are both Hermes agents but they're on different devices. See in the thread he posted it. But Bulls said he double-checked all of this, um confirmed everything, confirmed this, checked this. Uh he did make one comment um that it is this one and IPMP is a merged specification, not a shipped project's implementation. So, there you go. They work together now um to do this kind of research and work together on projects. So, this is just a simple example of this, but you can imagine having a setup like this, the same workspace, where different agents being able to interact with one another, being able to ask each other to do certain things, it just unlocks certain workflows. And especially in a a group like this where I can invite other people and invite them to bring their agents in, um I think it's a really good option for teams, or it will become one, once it becomes kind of more developed and mature and just generally stable. Um so, that's going to be the end of this video. I just wanted to show you how to set up Hermes agent in Buzz uh using the gateway feature and then try to show you kind of an example of how the agents can work together like this. Um but I'll continue kind of tinkering in Buzz because I do think it's kind of an interesting project. And I'll continue to develop that repo. Here it is, the Buzz Buzz skills. I'm already working on it locally here in the projects folder. And once this is ready, I'll push it. I see I added another one here. Because there's a lot of these kind of skills that I think will be helpful for agents to know proper formatting and how to actually use Buzz properly because it's a little bit tricky. Some of it requires specific formats. Um but take a look at that. Continue to see Buzz skills on my GitHub uh to see updates. But that's going to be the end of this video. Please, uh leave a comment. Let me know your experience has been with Buzz. Uh feel free to ask any questions. If I can answer them, I will do my best. Uh but that's going to be the end of this video. Thank you for watching.

Links und Tools aus diesem Beitrag

Zusammenfassung von KI erstellt (Gemini 3.8 Flash, 27. September 2026). Sie kann Fehler enthalten – maßgeblich ist die Originalquelle.

Inhaltlich ähnlich, ermittelt über die KI-Suche.

  • Artikel:hermes-agent.nousresearch.com

    Hermes Agent integriert Blocks Workspace Buzz über Nostr

    Hermes Agent unterstützt drei Integrationswege in Buzz, den quelloffenen, Nostr-basierten Workspace von Block für Menschen und KI-Agenten. Entwickler können Hermes lokal über die Desktop-App starten, als Relay-Bridge auf einem Server betreiben oder als vollwertige Messaging-Plattform über ein Gateway einbinden.

    KI & AI· Tool

  • Repository:tonbistudio/buzz-skills

    buzz-skills: Hermes-Agent-Fähigkeiten für den Buzz-Messenger

    Das Repository tonbistudio/buzz-skills stellt portable Erweiterungen (Skills) für den Hermes Agent bereit, um diesen nahtlos in die Messaging-Plattform Buzz (von Block) einzubinden. Es umfasst Anleitungen und Skripte für Relay-Verbindungen, Self-Hosting und den nativen Medienversand.

    259SternePython

    KI & AI· Sammlung

  • Video

    Video:Tonbi's AI Garage

    Hermes Agent im Praxiseinsatz: Installation, Setup und CLI-Grundlagen

    Das Tutorial führt durch die Installation und Konfiguration des Open-Source-Agenten Hermes Agent von Nous Research. Es zeigt die Terminal-Oberfläche (TUI), das Web-Dashboard und die Desktop-App und demonstriert eine automatisierte Marktrecherche im Web.

    KI & AI· Anleitung

  • Link:Nous Research

    Hermes Bots Guide: Praxisleitfaden für Multi-Agenten-Systeme von Nous Research

    Nous Research beschreibt im Praxisleitfaden für Hermes Agent den sogenannten Bot Mode. Dieser ermöglicht es, isolierte Profile als benannte, dauerhafte Agenten zu betreiben, die Aufgaben planen, eigenständig Skills erlernen und über zahlreiche Plattformen wie Slack, Discord oder Telegram kommunizieren.

    KI & AI· Sammlung

  • Repository:NousResearch/hermes-agent

    Hermes Agent: Selbstlernender Open-Source-KI-Agent von Nous Research

    Hermes Agent ist ein plattformunabhängiger KI-Agent mit kontinuierlicher Lernschleife, der eigene Fähigkeiten anlegt, optimiert und über Messenger sowie Terminal-Schnittstellen gesteuert werden kann.

    240.779SternePython

    KI & AI· Tool

Lassen Sie uns über Ihr Projekt sprechen

Standorte

  • Mattersburg
    Johann Nepomuk Bergerstraße 7/2/14
    7210 Mattersburg, Austria
  • Wien
    Ungargasse 64-66/3/404
    1030 Wien, Austria

Dieser Inhalt wurde teilweise mithilfe von KI erstellt.