Editorial illustration for Nous Research Ships Three Hermes Agent Integration Paths for Block's Nostr Workspace
Nous Hermes Agent Integrates With Block's Nostr Workspace
Nous Research has shipped support for its Hermes Agent inside Buzz, Block's open source workspace where humans and AI agents post to the same channels using Nostr as the backbone. That detail matters more than it sounds: every message on Buzz is a signed event on a relay someone actually owns, and every account, human or bot, is a keypair rather than an API token issued by a platform. Bot-token auth disappears. Agents get their own identity, their own channel memberships, and a message history that can be audited like anyone else's.
Buzz carries an Apache-2.0 license and 18.8k GitHub stars. Hermes Agent is MIT licensed. Both are self-hostable now, which puts a solo developer with Buzz Desktop and a mid-market platform team running Postgres, Redis, and MinIO on roughly the same starting line, just with different scaling needs.
Nous built the connection three separate ways, splitting by where Hermes actually runs and how it reaches the relay. The first of those paths starts with Buzz Desktop's managed runtime, spawning Hermes as a local preset harness the moment you open Settings.
Nous Research has released Hermes Agent support for Buzz, Block’s open source, self-hostable workspace where humans and AI agents share the same channels.
Why this matters
For teams building with agents, the identity model here matters more than the integration count. Bot tokens have always been a workaround, a human credential wearing a mustache. Giving Hermes its own keypair, its own channel memberships, and its own signed history on a relay you control changes what "agent access" even means: it's infrastructure-level accountability, not app-level permissions bolted on after the fact. That's worth watching closely if you're building anything where an agent touches production code or customer-facing systems, because "branch-as-room code review" and cron-delivered reports only stay useful if the audit trail is actually trustworthy.
The self-hostable, Apache-2 stack is the other detail worth noting. Nous and Block aren't asking anyone to trust a hosted API for agent identity, which is a real departure from how most agent tooling ships today. Whether three deployment paths translate into actual adoption outside crypto-adjacent dev circles is the open question. Nostr's relay model is unfamiliar to most teams, and unfamiliar infrastructure is a real adoption tax, protocol elegance aside.
Related Reading
Open Source D&B rebuilds 642 million‑business database after AI agents hit limits
Open Source OpenAI's GPT Transcribe Cuts Error Rate to 3.31%, Improving on GPT-4o
Open Source Study: 6.7% of Deepfake Requests on Hugging Face Targeted Children
From Archives PolyAI's Dialog-RSN-1 Fuses Speech Recognition and Response
From Archives Deep Agents v0.7 Updates Base Input Tokens, Performance Validated
Common Questions Answered
What are the three integration paths Nous Research shipped for Hermes Agent in Buzz?
While the article mentions that Nous Research has shipped three integration paths for Hermes Agent support within Buzz, the specific details of each path are not explicitly outlined in the provided content. The focus is on how these integrations enable Hermes Agent to function within Block's open source Nostr workspace alongside human users.
How does Nostr's relay-based architecture differ from traditional bot token authentication in Buzz?
In Buzz, every message is a signed event on a relay that someone actually owns, rather than being managed through platform-issued API tokens. This means agents get their own keypair identity instead of using bot tokens, providing infrastructure-level accountability and eliminating the need for workaround credentials.
What identity model advantages does Hermes Agent gain by having its own keypair in Buzz?
By receiving its own keypair rather than relying on bot token authentication, Hermes Agent gains independent channel memberships, its own signed message history on controlled relays, and true infrastructure-level accountability. This represents a fundamental shift from app-level permissions bolted on after the fact to genuine agent identity within the system.
Why does the article emphasize that Buzz is self-hostable and open source?
The self-hostable and open source nature of Buzz means teams retain control over their relay infrastructure and can verify the authenticity of all signed events, including those from AI agents. This architectural choice enables the decentralized identity model where agents and humans operate with equal standing on the same channels.
Further Reading
- Buzz Integration | Hermes Agent - Nous Research
- Hermes Agent now runs Buzz - Nous Research on X
- Integrations | Hermes Agent - Nous Research
- Programmatic Integration | Hermes Agent - Nous Research
- The Agent That Grows With You - Nous Research
