bzz

a human-first terminal client for Buzz

$ curl -fsSL https://getbzz.dev/install.sh | sh

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.

1Rust binary
60built-in themes
offlineSQLite-backed history
100%keyboard-driven
new in v0.15.0

Your own agents, run by bzz.

/// create

An agent with one command

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.

/// one reply

One reply per mention

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.

/// its own disk

A disk of its own, with git

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.

/// hands

Real commands, by your yes

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.

/// move

Move it, with its memory

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.

/// harnesses

Pi, Grok, Codex, Claude Code

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.

agent harnesses

Four ways to run an agent. One set of rules.

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.

/// pi durable default · everything in v0.15.0

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.

  • It survives a restart. Its conversations, a turn that was cut off, and its disk.
  • A disk of its own. One SQLite file, with a shell of about 80 commands and git over HTTPS. No program of your machine is started for it.
  • Nothing of yours by default. A folder, a host, a private repository or a real command: only what you grant, and a real command only after your yes.
  • It moves with its memory. bzz agent move to another bzz, or bzz agent launch-kit for a machine that runs Buzz's own buzz-acp.
  • Your model, your sign-in. Any model you are signed in to with Pi. bzz stores no provider key.
$ bzz agent new Scout --model openai-codex/gpt-6-luna
/// grok supported

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.

/// codex experimental

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.

/// claude code experimental

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.

Pi Durable Grok · Codex · Claude Code
where it works its own disk, in one SQLite file a real folder bzz makes, plus the folders you grant
what runs on your machine nothing, unless you grant a folder for commands a real shell, as your user
after a restart conversations, a cut-off turn and the disk the program's own saved session of each conversation
move to another machine yes, with its key, memory and disk no: its memory belongs to the program
the model any model of your Pi sign-in the models that program offers, with your sign-in there

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.

why bzz

Your keys, your history, your terminal.

/// identity

Native Nostr identity, in your OS keychain

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.

/// communities

Host-isolated communities

Each Buzz community stays isolated by host. Configure several, authenticate one active session, and switch without mixing state.

/// offline

Offline-first everything

Channel history, profiles, threads, unread markers, and drafts are cached locally. Read and draft on a plane; sync when you reconnect.

what you get

All of Buzz, at terminal speed.

/// sends

Acknowledged sends, honest failures

Durable ambiguous-outcome recovery with distinct pending, delivery-unknown, and rejected presentation. You always know what the relay actually accepted.

/// inbox

An Inbox that respects your attention

Mentions, relevant threads, workspace DMs, needs-action events, unread rows, and drafts — filterable, with explicit read/unread state. Nothing is silently marked read.

/// search

Unified local + relay search

Offline SQLite FTS5 plus authenticated NIP-50 prefix search across channels, DMs, people, and messages, with from:, in:, and date operators.

/// dms

Workspace DMs, honestly labeled

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.

/// media

Inline images, verified first

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.

/// attachments

Safe uploads, sanitized by default

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.

/// navigation

Vim-style, leader-key driven

j/k to move, Space Space for the fuzzy switcher, i to write, ? for the generated keymap help. Mouse optional, semantic, and safely restored.

/// themes

60 built-in themes

Plus semantic theme.toml customization. This page's theme switcher uses the same palettes — try it in the nav.

/// reactions

Reactions, deletion, read state

Reaction toggles, own-message deletion, and encrypted cross-device read state, all from the keyboard.

security

Security is a feature, not a footnote.

keybindings

Everything is a keystroke away.

Movement

j k
move down / up
1–4
focus workspace surfaces
Tab h l
traverse surfaces
gg G
jump to edges

Leader

Space Space
fuzzy channel/DM switcher
Space n
open Inbox
Space a
contextual actions
Space o
theme options
?
effective-keymap help

Messages

r
reactions
e
edit your message
y
copy sanitized text (OSC 52)
v
multi-message copy range
@
member completion

Composer

i
open the writing dock
Ctrl-o
OS file chooser
Ctrl-v
paste file / image / text
Ctrl-r
retry failed uploads
install

One binary. Pick your platform.

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).

/// verify

Verify what you run

Every release ships sha256.sum, a CycloneDX SBOM (bzz.cdx.xml), and GitHub build-provenance attestations. Verification steps live in docs/releasing.md.

/// first run

Then get connected

bzz identity new --label personal
bzz community add my-team \
  wss://my-team.communities.buzz.xyz <identity-id>
bzz