Unmute for narration. The real bzz 0.15.0 binary on a test relay with generated people and avatars; the agent's replies come from a real model. Voice: Fish Audio Drama 3 · music: ACE-Step.
bzz agent new, or :agent new in the TUI,
creates an agent in your team's Buzz. bzz holds its key, runs it on your
machine and signs what it says. Your team mentions it like any other
member.
The reply is signed and stored before it is published. Kill the agent or bzz at any moment: the same reply goes out again and the relay keeps one. You choose who may wake it; by default, only you.
The agent works on its own disk, with a shell and a
git that start no program of your machine. It sees a
folder of yours, a host or a private repository only when you grant
it.
Grant a folder for commands and each one waits for you.
Ctrl-y shows the whole command exactly as the shell will
get it; a allows it, r refuses it with a
reason.
bzz agent move seals the key, the memory and the disk
in one file for another bzz of yours. bzz agent launch-kit
runs it under Buzz's own buzz-acp on a machine without
bzz.
bzz's own host runs on Pi Durable. Or use a coding program you have installed and signed in to: Grok, and experimentally Codex and Claude Code. bzz says what each one can reach before you confirm. Compare them.
Agents need Node.js 22.19 or newer; bzz without agents stays one binary. Full notes: bzz v0.15.0 release.
A harness is the program that runs your agent's model and its tools. bzz drives all four over one protocol (ACP), and the same rules hold on each: bzz holds the agent's key, a mention gets one final reply, and you choose who may wake it.
bzz's own agent host is built on Pi Durable, which commits every conversation, model turn and tool call to storage before anything is shown. Close bzz, kill the process, restart the machine: the agent goes on from where it was.
git over HTTPS. No program of your machine is
started for it.bzz agent move to
another bzz, or bzz agent launch-kit for a machine that
runs Buzz's own buzz-acp.bzz agent new Scout --model openai-codex/gpt-6-luna
Your installed grok, with your own sign-in. It works
inside Grok's own sandbox: bzz writes the sandbox profile before every
start and keeps the folder of bzz's keys out of it.
Your installed codex, with your own sign-in. bzz sets
Codex's workspace-write mode on every conversation. What
would leave that sandbox is refused, or asked of you first.
Your installed claude, with your own sign-in. It has no
sandbox of its own, so bzz answers each of its requests by rule: edits
only in the folders you granted, commands only by your yes.
A coding harness is your own program at work on your own machine: bzz never gives it the agent's key, and cannot promise the key is out of its reach. The three were tried on Linux, at one version each. What each can read and write is in the agents guide.
Use your Nostr identity; communities may also require browser sign-in.
Local secret keys live in the operating-system credential store and never
pass through argv or plain environment variables. Backups are
password-encrypted NIP-49 ncryptsec files.
Each Buzz community stays isolated by host. Configure several, authenticate one active session, and switch without mixing state.
Channel history, profiles, threads, unread markers, and drafts are cached locally. Read and draft on a plane; sync when you reconnect.
Durable ambiguous-outcome recovery with distinct pending, delivery-unknown, and rejected presentation. You always know what the relay actually accepted.
Mentions, relevant threads, workspace DMs, needs-action events, unread rows, and drafts — filterable, with explicit read/unread state. Nothing is silently marked read.
Offline SQLite FTS5 plus authenticated NIP-50 prefix search across
channels, DMs, people, and messages, with from:, in:,
and date operators.
Buzz Desktop-compatible one-to-one and group DMs with owner-only hide state — and explicit labeling that they are not end-to-end encrypted.
JPEG/PNG/GIF/WebP render through Kitty, Sixel, iTerm2, or a Unicode half-block fallback. Every blob is size, MIME, and SHA-256 verified before decode or display.
Paste files or images with Ctrl-V, pick with the OS chooser.
Local images are bounded, orientation-corrected, and stripped of
private metadata before upload.
j/k to move, Space Space for the fuzzy
switcher, i to write, ? for the generated keymap help.
Mouse optional, semantic, and safely restored.
Plus semantic theme.toml customization. This page's theme
switcher uses the same palettes — try it in the nav.
Reaction toggles, own-message deletion, and encrypted cross-device read state, all from the keyboard.
curl -fsSL https://getbzz.dev/install.sh | sh
Detects OS and architecture. Read it first if you prefer: install.sh (redirects to the latest signed GitHub release installer).
# Apple Silicon
curl -fsSL https://github.com/arpagon/bzz/releases/latest/download/bzz-aarch64-apple-darwin.tar.xz | tar xJ
# Intel
curl -fsSL https://github.com/arpagon/bzz/releases/latest/download/bzz-x86_64-apple-darwin.tar.xz | tar xJ
sudo mv bzz /usr/local/bin/
# x86_64
curl -fsSL https://github.com/arpagon/bzz/releases/latest/download/bzz-x86_64-unknown-linux-gnu.tar.xz | tar xJ
# arm64
curl -fsSL https://github.com/arpagon/bzz/releases/latest/download/bzz-aarch64-unknown-linux-gnu.tar.xz | tar xJ
sudo mv bzz /usr/local/bin/
Linux builds require glibc 2.35 or newer and ALSA's
libasound.so.2 for huddle audio (Ubuntu 22.04+). No separate
DBus development package is needed.
powershell -ExecutionPolicy Bypass -c "irm https://github.com/arpagon/bzz/releases/latest/download/bzz-installer.ps1 | iex"
Or download bzz-x86_64-pc-windows-msvc.zip from the
latest release
and add bzz.exe to your PATH.
cargo install --git https://github.com/arpagon/bzz --locked
Builds locally with the pinned toolchain
(rust-toolchain.toml).
Every release ships sha256.sum, a CycloneDX SBOM
(bzz.cdx.xml), and GitHub build-provenance attestations.
Verification steps live in
docs/releasing.md.
bzz identity new --label personal
bzz community add my-team \
wss://my-team.communities.buzz.xyz <identity-id>
bzz