Hermes agents on Buzz get their own keys, not bot tokens — and that changes everything

Nous Research just shipped Hermes Agent support for Buzz, and the architecture flips the standard bot model on its head. Instead of dangling off a bot token with borrowed permissions, every Hermes agent on Buzz is a first-class Nostr keypair. It joins channels. It has its own membership. Every message is a signed event on a relay you control. You get an audit trail that actually means something.

Three connection paths cover the spectrum from solo tinkering to mid-market platform work. Buzz Desktop handles the lightweight case — it spawns Hermes locally as a preset harness, discovers the launcher on your PATH, and communicates over ACP via stdio. Tool permissions auto-approve, so Nous is explicit: keep this owner-only. The relay bridge lets you host an agent identity separately, bridging a channel to the Hermes host over WebSocket without a second install. The shared subprocess keeps its config, memory, skills, and state intact. The deepest integration is the native gateway, where a bundled plugin treats Buzz like any other Hermes messaging platform alongside Telegram and Discord. Channels, DMs, threads, reactions, images, cron delivery — it’s all there.

Defaults ship locked down. The agent answers in channels only when mentioned, access is gated to an allow-list of npubs or hex pubkeys, and tool progress logs stay out of the channel. Inbound on the gateway path rides a NIP-42-authenticated Nostr WebSocket with BIP-340 signing — no dependencies — falling back to CLI polling every four seconds. Outbound always goes through the buzz CLI.

Who’s this for right now? Solo devs can run it on Buzz Desktop with zero config. The sweet spot is small engineering teams who want incident memory over channel history, branch-as-room code reviews, or agent-drafted release notes. Enterprises should treat this as a pilot — mobile clients and workflow approval gates are still being wired up. But the foundation is genuinely different. An agent with its own keys, its own addressable identity, and its own verifiable history is a long way from a Slack bot with a token stuffed in an environment variable.