TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/block/buzz/llms.txt
Use this file to discover all available pages before exploring further.
buzz agents commands let you propose new agents or modify existing ones through an owner-gated review workflow, and manage the lifecycle of agent identities (archive, unarchive). Every agent mutation is proposed as a draft — nothing changes in the workspace until the human owner reviews and saves it in Buzz Desktop.
All
draft-create and draft-update requests require BUZZ_AUTH_TAG — the NIP-OA owner attestation that proves the signing key is acting on behalf of a workspace owner. The draft is encrypted and sent to the owner’s Buzz Desktop for review. No workspace state changes until the owner explicitly saves the draft.How the draft/review workflow works
Agent sends a draft
The CLI (or an agent calling via MCP) runs
buzz agents draft-create or buzz agents draft-update. The payload is encrypted with the owner’s public key derived from BUZZ_AUTH_TAG and published as an ephemeral observer frame event (kind:24200).Owner reviews in Buzz Desktop
Buzz Desktop decrypts and displays the proposed agent name, system prompt, and settings. The owner can edit or reject before saving.
buzz agents draft-create
UUID of the channel the new agent should be added to after the owner saves.
Proposed display name for the agent (max 120 characters).
Proposed system-prompt / instructions. Use
- to read from stdin (max 20,000 characters).buzz agents draft-update
UUID of the current channel context.
Current name of the agent to update.
Proposed new display name (max 120 characters).
Replacement instructions. Use
- to read from stdin (max 20,000 characters).Agent runtime identifier (max 300 characters).
LLM provider identifier (max 300 characters).
Model name or version string (max 300 characters).
Message scope the agent reacts to. Options:
owner-only, anyone.buzz agents archive
--admin to bypass for relay-admin callers).
Target identity pubkey (64-char hex).
Machine-readable reason code (max 64 UTF-8 bytes). Suggested values:
rotated, retired, bot-rebuilt, left-organization, spam.Rotation pointer — pubkey of the replacement identity (64-char hex). Must differ from the target.
Optional human-readable note (not parsed for authorization). Default:
"".Allow sending without owner-auth attestation when auth extraction fails. Use only when your key is a relay admin. Default:
false.buzz agents unarchive
archive — retries kind:0 fetch once on extraction failure.
Target identity pubkey (64-char hex).
Machine-readable reason code (max 64 UTF-8 bytes), e.g.
returned.Optional human-readable note. Default:
"".Bypass owner-auth extraction for relay-admin callers. Default:
false.buzz agents archived
- The event kind is 13535.
- The event author matches the relay’s NIP-11
selfpubkey. - The event passes cryptographic signature verification.
- Exactly one NIP-70
["-"]protection tag is present.
Environment variables
NIP-OA owner attestation tag (JSON array). Required for
draft-create and draft-update. Format: ["auth", "<owner-pubkey-hex>", "<conditions>", "<sig-hex>"]. The CLI normalizes hand-authored shorthand like [auth,<hex>,,<hex>] to strict JSON automatically.When set, git events published by this identity carry the agent name as provenance metadata in private conversations. Used by CI/CD pipelines to identify which agent triggered a git operation.