Nous Research Ships Three Integration Paths for Hermes Agent and Buzz
Block's open-source Nostr workspace for humans and agents now offers desktop, relay, and native gateway integration options.
Stock photo for illustration only, not from the actual event
- Both Buzz and Hermes Agent are fully self-hostable today.
- Integrations are split into three paths: Buzz Desktop, Relay Bridge, and Native Gateway.
- Default configurations prioritize security with strict mention and access controls.
- The underlying relay architecture runs on Postgres, Redis, and S3/MinIO.
Nous Research and Block have introduced three distinct integration pathways connecting the Hermes Agent with Buzz, an open-source Nostr workspace built for both humans and AI agents. Both applications are fully self-hostable out of the box, with Buzz utilizing the Apache-2.0 license boasting 18.8k GitHub stars, while the Hermes Agent operates under the MIT license. This setup allows solo developers and small engineering teams to run the system through Buzz Desktop with zero configuration required.
Mid-market platform teams represent the ideal target audience because the underlying relay relies on Postgres, Redis, and S3/MinIO. Meanwhile, enterprises should approach this as a pilot project, as mobile clients and workflow approval gates are still actively being integrated. Practical use cases range from incident memory over channel history and branch-as-room code reviews to agent-drafted release notes and cron-delivered reports.
The integration documentation divides the setup procedure based on where Hermes executes. The first option is the Buzz Desktop Managed Runtime, where Buzz spawns Hermes locally as a preset harness. Users can navigate to Settings and select Runtimes, causing Hermes to appear automatically. Discovery resolves the hermes-acp launcher on the login-shell PATH, which the installer writes directly to ~/.local/bin using ACP over stdio for inbound traffic.
Stock photo for illustration only, not from the actual event
The second option is the Relay Bridge, tailored for hosted agent identities. The buzz-acp harness bridges a channel to hermes acp over stdio, connecting to the relay via WebSocket. This serves as a transport integration rather than a secondary installation, allowing the spawned subprocess to share identical configurations, credentials, memory, skills, and state with Hermes on that host.
The multi-path integration strategy between Buzz and Hermes Agent highlights the growing industry shift toward decentralized protocols like Nostr for AI agent orchestration. By bypassing closed ecosystems, developers gain granular control over data privacy and infrastructure, making it particularly appealing for organizations deploying autonomous agents in sensitive environments.
The deepest option is the Native Gateway Platform, which integrates a bundled Buzz plugin to make Buzz a primary messaging platform for Hermes alongside Telegram and Discord. It supports channels, direct messages, mention gating, threaded replies, reactions, images, and cron delivery, while Hermes maintains its independent approvals, memory, and session management via the hermes gateway setup command.
On the gateway route, inbound data arrives through a persistent NIP-42-authenticated Nostr WebSocket utilizing dependency-free BIP-340 signing, with automatic fallback to CLI polling. Recommended default settings ship in private mode, where require_mention is set to true so the agent only replies when directly addressed in channels, while allow_all_users is set to false to restrict access strictly to approved public keys.
Source: MarkTechPost
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment