Nous Research Integrates Hermes Agent with Buzz Nostr Workspace

Nous Research has released support for its Hermes Agent to integrate with Buzz, an open-source, self-hostable workspace developed by Block. Buzz is designed to enable humans and AI agents to share the same communication channels, operating on the Nostr protocol. In Buzz, every message is a signed event stored on a user-owned relay, and each participant, whether human or agent, is identified by a keypair, thereby eliminating the traditional bot-token model. This approach grants agents distinct identities, channel memberships, and an auditable history of their actions. The integration is deployable for both solo developers and small engineering teams using Buzz Desktop, which requires no configuration. Mid-market platform teams are identified as a strong fit, particularly due to Buzz's reliance on Postgres, Redis, and S3/MinIO for its relay infrastructure. For enterprises, Nous Research suggests scoping this integration as a pilot project, as features such as mobile client support and workflow approval gates are still under development. Potential practical applications for this integration include maintaining incident memory through channel history, conducting code reviews within dedicated branch-as-room setups, generating agent-drafted release notes, and scheduling cron-delivered reports. Nous Research has outlined three distinct methods for connecting Hermes Agent to Buzz, categorized by where the Hermes Agent is executed. The first path involves the Buzz Desktop managed runtime, where Buzz automatically spawns Hermes locally as a preset harness. Users can access this by navigating to Settings → Runtimes, and Hermes will appear. The installer places the hermes-acp launcher in the user's login-shell PATH, typically in ~/.local/bin, enabling inbound communication via ACP over stdio. The second integration method, termed the relay bridge, is suitable for a hosted agent identity. In this scenario, Buzz's buzz-acp harness acts as a bridge, connecting a communication channel to Hermes ACP over stdio, with communication to the relay established via WebSocket. This method focuses on transport integration rather than requiring a separate installation of Hermes, allowing the spawned subprocess to share the same configuration, credentials, memory, skills, and state as the Hermes instance on that host. The third and most deeply integrated option is the native gateway platform. This involves a bundled Buzz plugin that transforms Buzz into a fully functional Hermes messaging platform, operating alongside existing services like Telegram and Discord. This integration covers a comprehensive range of features, including channel management, direct messaging, mention gating, threaded replies, message reactions, image sharing, and cron-based delivery. Within this native gateway, Hermes independently manages its own approval workflows, memory, and state.