Nous Research Hermes Agent has been released for BuzzBlock’s self-hosted workspace is open source and allows both humans and artificial intelligence agents to use the same channels. Buzz was built using Nostr. The message you send is the event that is signed on your relay, and each participant, whether human or an agent, represents a key pair. The bot token model is eliminated. Each agent has their own unique identity and channel memberships. They also have their own audit trail.
Can it be deployed, and by whom?
Both sides can be self-hosted today. Buzz Apache 2.0 with 18,8k stars Hermes Agent MIT License. Buzz Desktop can be used by small and solo engineering teams. The relay is best suited for mid-market platforms, as it runs on Postgres Redis and S3/MinIO. Since mobile apps and workflow gates are not fully wired, enterprises should consider this as a test. Some practical applications are incident memory for channel history, branch as room code review, release notes drafted by agents, and reports delivered via cron.
There are three different ways you can connect
It is important to note that the word “you” means “you”. integration docs Divide the work according to where Hermes is running.
The Underside of the Buzz Desktop runtime managedBuzz will create Hermes in your local area as a harness that you have previously set. Open Settings → Runtimes Hermes will appear automatically. Discovery is the solution to this problem. hermes-acp Launcher in your PATH (which the installer writes) ~/.local/bin. Inbound travel is ACP Over stdio
It is important to note that the word “you” means “you”. Relay bridge A hosted agent identity. Buzz’s buzz-acp Harness bridges is a way to Hermes acp WebSockets are used for the transfer of data over Stdio. It is not a new installation, but a transport-integration. It shares the same credentials, state, skill, memory as well as configuration. Hermes The host is on.
It is important to note that the word “you” means “you”. Native Gateway Platform This is the most comprehensive option. The bundle buzz Buzz becomes a standard Hermes platform, alongside Telegram and Discord. It covers channels, DMs and mention gating. Hermes maintains control over its approvals, session management and memory. The setup is easy. Hermes Gateway Setup.
Transport, defaults and Identity
Inbound traffic arrives via a Nostr WebSocket that is persistently authenticated with NIP 42 and BIP 340, but without any dependency. The gateway will automatically fall back to CLI-polling. Outbound is always through buzz CLI. The Transportation Setting Acceptance You can also find out more about the automakers by clicking here., WebsocketIf you want to know more about. Poll” poll_interval The default is 4 seconds.
This is a recommended article defaults Ship private. "require_mention": true The agent will only answer if he is addressed directly in the channel, and DMs are always dispatched. Allow_all_users is false Restricts access to the listed pubkeys and npubs. interim_assistant_messages: false You can also find out more about the following: Off tool_progress Keep the log of the tool out of the channels. Event ids are used to compare against the channel high water mark and pubkey is used to filter agent messages.
What you need to know
- Hermes Agent is connected to Buzz via three methods: Desktop Runtime, Relay Bridge, and Native Gateway.
- Hermes, its skills, sessions, cron and session memory are preserved by the Gateway path.
- Inbound utilizes a NIP 42 Nostr web socket, and CLI polling falls back at 4 seconds.
- The defaults are set to private. They include mention-gating, enforced allow list, and suppressed tool logs.
- Buzz Desktop will automatically accept tool permissions. Agents should only be owned by Buzz Desktop.
Click here to find out more Integration DocsThe Buzz Adapter ReferenceAnd the GitHub Repo. You can also follow us via TwitterJoin our. SubReddit Subscribing to our Newsletter Newsletter.

