Nous Research integrates Hermes Agent with Nostr-based Buzz workspace
Open-source AI systems just got a new identity layer. Nous Research has released Hermes Agent support for Buzz, Block’s self-hostable workspace where humans and AI agents operate under the same cryptographic identities on the Nostr protocol. Every participant, whether human or autonomous agent, is a keypair, and every message is a signed event on a relay you control. The move replaces the traditional bot-token model with a permissionless, self-auditable environment.
A workspace built for humans and agents
Buzz runs on Nostr, meaning messages are verifiable, portable, and resistant to central control. Instead of assigning tokens to bots, Buzz grants each agent its own identity, channel memberships, and immutable message history. The system is already Apache-2.0 licensed with nearly 19k GitHub stars, while Hermes Agent ships under MIT. Deployment scales from solo developers running Buzz Desktop with zero configuration to mid-market teams using Postgres-backed relays and Redis caching. Enterprises are advised to treat this as a pilot until mobile clients and workflow approval gates mature.
Three ways to connect Hermes to Buzz
The integration offers three paths depending on where Hermes runs. Under Buzz Desktop, Hermes spawns automatically as a preset runtime once enabled in Settings → Runtimes. For hosted agents, the relay bridge forwards messages over a WebSocket using a buzz-acp harness, sharing config, credentials, and state with the local Hermes instance. The deepest integration is the native gateway, which embeds Buzz as a first-class Hermes messaging platform alongside Telegram and Discord. It handles channels, DMs, threaded replies, reactions, images, and cron delivery while preserving Hermes’ approvals, memory, and session management.
Transport, defaults, and identity
On the gateway path, inbound messages arrive via a persistent NIP-42-authenticated Nostr WebSocket, falling back to CLI polling every four seconds. Outbound always uses the Buzz CLI. Administrators can toggle transport modes (auto, websocket, poll), set mention gating, restrict access to specific npubs or hex pubkeys, and suppress tool logs from channels. Events are de-duplicated by event ID against a per-channel watermark, and agents ignore their own messages by pubkey.
Why it matters
Source: MarkTechPost. AI-assisted editorial synthesis — TechnoExpress.

