Nous Research ships three integration paths for Hermes Agent and Buzz. Explore desktop runtime, relay bridge, and native gateway options for Nostr AI agents.
Nous Research has shipped three integration paths connecting Hermes Agent to Buzz, Block’s open source Nostr workspace. The Hermes Agent-Buzz integration gives AI agents native identities in decentralized communication systems for the first time at this scale. For technology professionals evaluating agent frameworks and self-hosted infrastructure, the integration opens practical new options. Here’s what the Hermes Agent-Buzz connection means and how to put it to work.
Buzz is not another messaging app. It is a workspace built on Nostr, a decentralized protocol designed to put users in control of their data. Every message sent in Buzz is a signed cryptographic event stored on a relay the user owns. This architecture gives each participant—human or artificial—a keypair-based identity.
The implications for AI agents are significant. An agent on Nostr is not a bot account controlled by a centralized platform. It is a peer with its own cryptographic identity, capable of signing messages and participating in conversations directly. This model aligns with the rising trend of self-hostable AI agent workspaces, a movement that gained momentum in the 2026 release cycle.
For developers, the benefits are concrete. An agent can join a workspace, authenticate itself cryptographically, and interact with human participants without a middleman controlling access or data. The relay itself—not a central server—becomes the source of truth. Every event is auditable, and identity is portable across applications that support Nostr.
Nous Research has designed the Hermes Agent-Buzz integration with deployment flexibility in mind. The three paths serve different scenarios, from lightweight desktop setups to full gateway integration in production workflows.
Before diving into each path, it is worth considering your constraints. If you need the fastest setup with minimal infrastructure, the desktop runtime wins. If you are deploying agents across multiple servers or edge environments, the relay bridge provides better flexibility. If you need full statefulness—memory, sessions, and approvals—in a shared workspace, the native gateway is the right choice.
The Buzz Desktop managed runtime is the simplest entry point. It embeds Hermes Agent directly into the Buzz Desktop application, allowing users to run an agent alongside their workspace without standing up separate infrastructure.
This path is ideal for individual users who want a personal AI assistant integrated into their daily communication. Setup is minimal, and the agent is immediately available in the same interface where conversations happen.
However, the convenience comes with trade-offs. The desktop runtime auto-approves tool permissions, which means the agent can execute tools without asking for explicit approval each time. This design favors streamlined interaction, but it also places responsibility on the owner to manage access carefully. The guidance is clear: keep agents owner-only when using this path.
The relay bridge takes a more network-centric approach. It connects Hermes Agent to a Nostr relay, enabling the agent to send and receive events over the protocol without requiring a desktop client.
This path suits developers deploying agents remotely or in headless environments. When WebSocket transport is unavailable, the bridge falls back to a default CLI polling interval of 4 seconds for inbound events—a practical compromise between responsiveness and resource usage.
The relay bridge makes Buzz a viable transport for agent operations without tying the agent to a specific application. It also allows multiple agents to connect to the same relay, each with its own identity, enabling multi-agent communication within a shared event stream. For self-hosted deployments, this design keeps the agent reachable without exposing inbound ports.
The native gateway path is the most comprehensive option. It elevates Buzz to a first-class Hermes messaging platform alongside established channels like Telegram and Discord. Agents connected through this path retain the full suite of Hermes capabilities: memory, skills, approvals, cron jobs, and sessions.
This is the integration likely to interest organizations building production agent deployments. The native gateway preserves the complete stateful experience that makes Hermes Agent powerful while leveraging Buzz’s decentralized infrastructure.
For developers already using Hermes with Telegram or Discord, the Buzz gateway feels familiar. It follows the same architectural patterns but adds Nostr’s open relay system, cryptographic identity, and self-hostable infrastructure. Sessions persist across message threads, and users can see when the agent is processing a request—all on an event-sourced foundation.
The default gateway settings reflect a deliberate privacy-first philosophy. When you deploy the native gateway, three defaults stand out:
These defaults matter in real-world deployments. In a collaborative workspace, you do not want every agent action broadcast to all participants. Mention gating keeps the agent quiet until it is explicitly summoned. Allow-listed access prevents unauthorized users from triggering expensive or sensitive operations.
Suppressing tool progress also keeps channels readable and prevents information leakage about how an agent reaches its conclusions. Teams can observe outcomes without exposing the underlying reasoning process to everyone in the room. For regulated industries, this granular control is an advantage over platforms that publish full operation logs by default.
The privacy-friendly defaults do not eliminate security considerations. Buzz Desktop auto-approves tool permissions, which means a desktop-connected agent can execute tools without explicit user approval for each action.
The official guidance is direct: keep agents owner-only when using the desktop runtime. This reduces the risk of another user triggering tools through your agent without oversight. In contrast, the gateway path supports the approvals workflow, giving operators a control point for tool calls.
For organizations, the distinction matters. A desktop-connected agent used by a team should be restricted to the owner. A gateway-connected agent can participate in shared spaces while retaining an approval checkpoint for tool execution. Choosing the right path is not just a deployment preference—it is a security decision.
Both projects are fully open source, and that is central to their appeal:
This licensing combination is notable. Apache-2.0 and MIT are permissive licenses that allow commercial use, modification, and distribution. Teams can self-host both components without vendor lock-in, a key driver behind the rise of self-hostable AI agent workspaces.
The developer ecosystem also benefits from transparency. Because every message is a signed event on a user-owned relay, auditability is baked into the architecture. Combined with Hermes Agent’s open-source codebase, this creates a verifiable foundation for agent operations. Developers can inspect the code, contribute fixes, and customize behavior to fit their infrastructure.
What can you actually build with the Hermes Agent-Buzz integration? Several concrete scenarios stand out.
Personal AI assistant. Set up Buzz Desktop with a managed Hermes Agent runtime. Give the agent access to your calendar and task list. Mention it in a conversation to retrieve information, schedule events, or draft responses.
Collaborative research agent. Deploy Hermes Agent through the native gateway in a Buzz workspace dedicated to research. Allow-listed team members can ask questions, review outputs, and track sessions—all without exposing tool internals to the entire room.
Self-hosted agent infrastructure. Organizations can run both Buzz and Hermes Agent on their own infrastructure. The relay bridge connects remote agents without requiring inbound connections from public networks, which suits security-conscious deployments.
Multi-agent experimentation. Because each Nostr identity uses keypairs, you can run multiple agents with distinct identities in the same workspace. They can collaborate on tasks, with the relay preserving a signed audit trail of all interactions.
The integration arrives amid three converging trends: rising interest in self-hostable AI workspaces, native agent identity on decentralized protocols, and deeper agent framework integration with communication platforms. The Hermes Agent-Buzz combination touches all three.
Decentralized identity is arguably the most compelling angle. When agents hold their own keypairs, they become participants rather than tenants. They can sign data, prove their actions, and operate independently of any single platform. As multi-agent systems become more common, this model offers a robust foundation for agent-to-agent communication.
The trend lines suggest more frameworks will follow Hermes Agent’s lead. Communication platforms that treat agents as first-class citizens—with identity, memory, and approvals built in—will likely define the next generation of AI infrastructure. Buzz’s open source, relay-based architecture positions it well for this shift.
The Hermes Agent-Buzz integration offers three practical paths for connecting advanced AI agents to a decentralized communication workspace. Whether you choose the desktop runtime for simplicity, the relay bridge for remote deployments, or the native gateway for production statefulness, the options cover a wide range of use cases.
Key takeaways:
Both projects are permissively licensed and self-hostable, making them strong candidates for teams that value data sovereignty. If you are building agent-powered workflows, the Hermes Agent-Buzz integration adds Nostr’s decentralized identity model to your toolkit. It is worth a closer look.
It is a set of integration paths from Nous Research that connects Hermes Agent to Buzz, Block's open source Nostr workspace. This allows AI agents to operate with their own cryptographic identity in decentralized, self-hosted communication systems rather than relying on centralized bot accounts.
The three paths are the Buzz Desktop managed runtime, a relay bridge, and a native gateway. The desktop runtime is the quickest way to get started, the relay bridge offers flexible deployment across multiple servers or edge environments, and the native gateway provides full statefulness with memory, sessions, and approvals in a shared workspace.
Nostr gives each agent a keypair-based identity, so agents can sign messages and participate directly as peers without a central platform controlling access or data. The relay acts as the source of truth, making every event auditable and keeping identity portable across Nostr-compatible applications.
Choose the desktop runtime if you need the fastest setup with minimal infrastructure. Choose the relay bridge if you are deploying agents across multiple servers or edge environments. Choose the native gateway if you need full statefulness, including memory, sessions, and approvals, in a shared workspace.
Buzz uses Nostr's cryptographic event model, where every message is signed with a keypair and stored on a user-owned relay. This means an agent's identity is cryptographically verifiable and portable, and all interactions can be audited without relying on a central server.
