Set Up Buzz for Your Super Agent

Before You Start

Buzz is a supported Hermes messaging adapter. Before setup, install the `buzz` CLI binary on the agent host, get the Buzz community relay URL, and confirm that the identity for your Nostr private key is already a member of that community.

Treat the Nostr private key as a secret. Never paste it into Agentic Workers chat, support messages, screenshots, or team notes. Store it as `BUZZ_PRIVATE_KEY` in `~/.hermes/.env` on the agent host.

Run the Guided Hermes Setup

On the agent host, run `hermes gateway setup`, choose Buzz from Messaging Platforms, and follow the prompts. If the gateway service is not installed yet, the setup will offer to install it after you configure the platform.

Provide the Buzz community relay URL and non-secret channel settings when prompted. Put the Nostr private key only in `~/.hermes/.env`; do not enter it in chat or send it to support.

Configure and Start the Gateway

The guided setup writes the Buzz platform settings to the Hermes gateway configuration. You can also configure the `gateway.platforms.buzz` block in `config.yaml`, or use `BUZZ_*` environment variables such as `BUZZ_RELAY_URL`; environment variables override the file.

Start the gateway with `hermes gateway start`, then check it with `hermes gateway status`. Keep the private key in `~/.hermes/.env` regardless of whether the remaining settings live in `config.yaml` or environment variables.

Verify Before Team Use

Start with a low-risk, read-only request in a Buzz channel or direct message. Confirm it reaches the intended agent before inviting teammates or using production information.

Review the corresponding Agentic Workers trace and confirm the agent used only the expected tools. Keep external posting or other write actions approval-only until the test is repeatable.

Troubleshooting and Retry

If Buzz does not appear in the platform list, update Hermes and run `hermes gateway setup` again. Confirm that the `buzz` binary is on `PATH`, or set `BUZZ_CLI_PATH` to its location.

If the gateway cannot connect, verify the community relay URL and confirm that the Nostr identity is a member of that community. Correct the non-secret settings, restart the gateway, and check `hermes gateway status` before retrying a message.

If you ask support for help, include only the visible error, gateway status, and non-sensitive configuration details. Never send the Nostr private key; keep it in `~/.hermes/.env` and rotate it locally if you believe it was exposed.