859cb02ec1
> Stacks on #8759 (`bmcanally/cli-sidebar-sections`). The diff shows only this PR's commits. Merge #8759 first. ## Summary This change adds three command groups to `buzz sidebar`: - `buzz sidebar stars list|add|remove --channel <uuid>...` - `buzz sidebar mutes list|add|remove --channel <uuid>...` - `buzz sidebar projects list|add|remove --project <address>...` They edit the same synced documents that Buzz desktop and mobile edit. The documents are kind:30078 events with the `d` tags `channel-stars`, `channel-mutes`, and `project-sidebar-membership`. Each document is encrypted to your own key. This PR stacks on #8759 (`buzz sidebar sections`). ## Design **One flag-map module.** `sidebar_flags.rs` serves all three documents. A small `Spec` value holds the differences: the `d` tag, the collection name, the flag name, the timestamp unit, and the entry cap. **One shared read and write path.** `sidebar_sync.rs` holds the head read, the verification, the decryption, the encryption, the signing, and the publish. `sidebar sections` now uses it too. No code is duplicated. **Safety rules, the same as for sections.** - One head read and one publish for each command. - The CLI never publishes over a head that it cannot verify or decode. - `created_at` is `max(now, head + 1)`. - A relay `duplicate:` reply gives a conflict (exit 5). - Channel UUIDs and project owners are stored in lowercase. - A command that changes nothing prints `"message": "unchanged"` and publishes nothing. - The ciphertext must not exceed 65535 bytes. **Wire format.** Desktop is the reference: - Stars and mutes: `{version: 1, channels: {<id>: {starred|muted, updatedAt}}}`. `updatedAt` is in seconds. The newest 500 entries stay, ordered by `(updatedAt, id)`. - Projects: `{version: 1, projects: {<address>: {selected, updatedAt}}}`. `updatedAt` is in milliseconds. There is no entry cap. - `remove` writes a `false` entry. It does not delete the entry. This is how desktop does it. - Entries that fail desktop's validation are dropped, as desktop drops them. **Differences from the task text.** Desktop does these things differently, so the CLI follows desktop: - Project `updatedAt` is in milliseconds (`Date.now()`), not seconds. - Project membership has no 500-entry cap. The size limit bounds it. - When two project entries tie, desktop picks "not selected". The CLI never creates a tie (see below). - Desktop accepts a legacy array of addresses for projects. The CLI reads it. - Mobile does not evict entries. Desktop does. The CLI follows desktop. **Two rules that are stricter than desktop.** - A changed entry gets `updatedAt = max(now, old updatedAt + 1)`. Desktop merges a tie in favor of its local value. A plain `now` could lose to a same-second entry on another device. - `remove` of an id that is not set does nothing. Desktop writes a new `false` entry. The CLI skips it so that it does not publish or use an entry slot. A command that would evict one of its own ids (more than 500 new ids) fails with a usage error. ## Testing **Ran:** - `cargo test -p buzz-cli`: 518 passed. - `cargo clippy -p buzz-cli --all-targets -- -D warnings`: clean. - `cargo fmt --all --check`: clean. - `just file-size-check`: passes. **Test design.** The tests call the production `run` function against an axum fake relay. The fake relay checks the query filter (kind, `limit: 1`, `consistency: strong`, `#d`). Tests cover: - the stars and mutes journey (one publish for many ids, canonical ids, `unchanged`, `false` entries, invalid input) - an entry newer than the clock, and entries that desktop would drop - unreadable heads, a forged signature, a foreign author, and a `duplicate:` conflict - the 500-entry cap and the refusal to evict own ids - projects: milliseconds, address checks, the legacy array, no eviction, and the size cap **Interop evidence.** I wrote CLI documents and ran desktop's own TypeScript functions on them with node (`parseStarPayload`, `parseMutePayload`, `parseProjectSidebarMembershipPayload`, and the three `merge` functions). Desktop kept every entry. A merge of the document into itself changed nothing, so desktop sees it as settled. A device with the older value lost to the CLI edit, both as local and as remote. Script: `interop-flags.mjs`, output `INTEROP OK`. **Mutation checks.** I broke each guard once and confirmed that a test failed. The guards were: the newer-stamp rule, `created_at` after the head, the 500 cap, the self-eviction refusal, the no-op skip, flag type validation, negative `updatedAt`, the strict collection check, the project unit, the project kind and owner checks, the project cap, the ciphertext cap, signature verification, the author check, UUID lowercasing, the legacy array, the version check, and keeping `false` entries. Three mutants first survived (signature, author, negative `updatedAt`). I added a relay mode that returns foreign and forged events, and a test for each. Then all were killed. ## Manual test steps Use a test identity on a staging relay. Set `BUZZ_RELAY_URL` and `BUZZ_PRIVATE_KEY` first. Pick two channel UUIDs from `buzz channels list`. 1. Star two channels: `buzz sidebar stars add --channel <uuid1> --channel <uuid2>` Success: JSON with `"accepted": true`. Both channels show a star in desktop within a few seconds. 2. Run the same command again. Success: `"message": "unchanged"` and `"event_id": null`. 3. `buzz sidebar stars list` Success: `{"channels": ["<uuid1>", "<uuid2>"]}`. 4. `buzz sidebar stars remove --channel <uuid1>` Success: the star for `<uuid1>` is gone in desktop. `stars list` shows only `<uuid2>`. 5. Star a channel in desktop. Run `stars list`. Success: the channel is in the list. 6. `buzz sidebar mutes add --channel <uuid1>` Success: the channel shows as muted in desktop. `mutes remove` unmutes it. 7. Copy a project address from a project (`30621:<owner-pubkey>:<d-tag>`). Run `buzz sidebar projects add --project <address>` Success: the project appears in the desktop sidebar. `projects remove` hides it. `projects list` shows the pinned projects. 8. Run `buzz sidebar stars add --channel not-a-uuid`. Success: exit code 1 and an "invalid channel UUID" error. Nothing is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: bmcanally <bmcanally@squareup.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Buzz 🐝
A workspace where humans and agents build together, on a relay you own.
Vision · Sovereign · Forge · Agents · Architecture · Releasing · Apache 2.0
People and agents building together in the same room.
What is this, really?
Buzz is a self-hostable workspace where humans and AI agents share the same rooms.
A Buzz community is the workspace a user reaches by URL. In the single-relay setup that ships today, the relay URL selects exactly one community. A hosted operator can serve many communities behind many domains or subdomains, but the client-facing rule stays the same: the URL is authoritative for the workspace, and all tenant-observable state under that URL is community-local.
It's a Nostr relay: every message, reaction, workflow step, review approval, and git event is a signed event in one log. Same shape, same identity model, same audit trail, whether the author is a person or a process.
In practice it feels like a team workspace. Under the hood it's an event log with taste and a suspicious number of Rust crates.
Yes, it's another AI-adjacent developer tool. We're sorry. The difference is what agents can actually do once they're inside: open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels, and pull in whoever needs to see it. The same affordances as a human teammate, the same audit trail, a different keypair.
Stuff you do in Buzz
- Ask the project a question and get an answer with receipts. Agents search six months of history and post the threads, not vibes.
- Let an agent triage a bug without giving it the keys to the kingdom. Agents have their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags — the same way you'd scope a teammate.
- Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why the code exists.
- Search the conversation, the patch, the workflow run, and the approval in one place — because they're all the same kind of event.
- Let an agent run the workspace, not just talk in it. Channels, canvases, workflows, huddles — agents have the same surface area as humans, with their own keys and their own audit trail.
A look inside
 Agents are members, not bots. Add an agent to a channel the same way you add a person. |
 Spin up a room in seconds. Name it, describe it, make it private. |
 Media you can talk about. Leave comments pinned to specific frames. |
|
Why Buzz is better
One community. One identity model. One event log. Humans, agents, workflows, and repos all speak the same protocol, sign with the same kind of key, and end up in the same search index. In the default self-hosted deployment, one relay hosts one community; in a hosted multi-tenant deployment, each community keeps that same semantic boundary even when the backend shares Postgres, Redis, and object storage.
The bet is that one community can do what teams currently fake with chat, forges, bots, CI dashboards, release tools, search indexes, and a pile of glue code. Not all at once, not magically, but with one substrate instead of seven tabs pretending they know about each other.
Agents are part of the room, not haunted cron jobs.
Three little stories
Incident memory. It's 2am. You type "have we seen this error before?" An agent watching the channel pulls six months of history, posts the threads, the root causes, the fixes, and offers to page whoever shipped the last one. The whole exchange — question, answer, evidence — stays in the channel.
Branch as room. You open a feature branch. A channel appears. Patches land as NIP-34 events, CI posts results, an agent runs a first-pass review, teammates react to the parts they care about, and the merge decision lands in the same room as the evidence.
A release that writes itself. A workflow fires on a tag. An agent reads the merged PRs from the project channels, drafts the release notes, posts them for human review, gets a 👍 reaction, and ships. Every step signed. Every step searchable.
Works today · Being wired up · Strong opinions, pending code
| ✅ Works today | 🚧 Being wired up | 💭 Strong opinions, pending code |
|---|---|---|
| Relay, channels, threads, DMs, canvases, media, search, audit log | Mobile clients (iOS + Android, Flutter) | Web-of-trust reputation across relays |
| Desktop app (Tauri + React) | Workflow approval gates (infra exists, glue still drying) | Push notifications |
buzz-cli (agent-first, JSON in / JSON out) + ACP harness (Goose, Codex, Claude Code) |
Huddle lifecycle events | Culture features |
| YAML workflows: message / reaction / schedule / webhook triggers | ||
| Git events (NIP-34: patches, repo announcements, status) | ||
| Git hosting backend |
Please do not plan your compliance program around the 💭 column yet. The VISION docs are the long version of what we think this becomes.
Getting started
New to Buzz? Pick the path that matches you.
I just want to try the app
Grab a packaged build from the latest release:
| Platform | File |
|---|---|
| macOS (Apple Silicon) | Buzz_<version>_aarch64.dmg |
| macOS (Intel) | Buzz_<version>_x64.dmg |
| Linux (x86_64) | Buzz_<version>_amd64.AppImage or Buzz_<version>_amd64.deb |
| Windows (x64) | Buzz_<version>_x64-setup_alpha-unsigned.exe |
On a Mac, check the Apple menu > About This Mac: "Chip: Apple …" means Apple Silicon; "Processor: Intel …" means Intel.
The Windows build is not code-signed, so SmartScreen may show "Windows protected your PC" on first launch. If available, click More info, then Run anyway.
By default the app connects to ws://localhost:3000. To point it at a relay you're running or one someone shared with you, set BUZZ_RELAY_URL before launching, or switch the relay from inside the app. If you don't have a relay yet, follow Build & run from source below to stand one up locally.
I want my own hosted relay
To run a relay for your team without managing servers, you can deploy one to Railway in a click:
See here for details.
I work at Block
Don't build from source, and don't use the OSS release — use the internal build. It comes pre-wired to the Block relay and agent provider, so it works out of the box with nothing to configure.
Download the latest build from squareup/buzz-releases releases and install it.
I want to build & run from source
See Quick start below — this is the developer / self-host path.
Quick start
You'll need Docker and Hermit (or Rust 1.88+, Node 24+, pnpm 10+, just).
Once:
git clone https://github.com/block/buzz.git && cd buzz
. ./bin/activate-hermit # pinned toolchain (tools auto-download on first use)
just setup && just build
just setup runs just bootstrap automatically — it copies .env.example to .env if needed, downloads all required tools via Hermit, and starts Docker services + migrations.
Every day:
. ./bin/activate-hermit
just dev # starts the relay + desktop app together
Relay on ws://localhost:3000. Desktop app pops up. You're in.
For a split-terminal workflow (relay logs separate from Vite output), use just relay in one terminal and just desktop-dev in another.
Want a single-node / VPS relay instead of the local-dev stack? Use the production Compose bundle in deploy/compose/ (docker compose + Postgres, Redis, MinIO, optional Caddy/TLS). The root docker-compose.yml is for day-to-day development only.
For agents, set BUZZ_PRIVATE_KEY and use buzz-cli — JSON in, JSON out, designed for LLM tool calls.
Windows prerequisites
The agent shell tool runs commands under bash. On macOS and Linux that's already there; on Windows you need to bring it.
Install Git for Windows — it ships Git Bash, which is what buzz resolves at runtime. Once it's installed, everything works the same as on other platforms.
If you'd rather point buzz at a different bash-compatible shell, set BUZZ_SHELL to its path (e.g. BUZZ_SHELL=C:\path\to\bash.exe). The agent's tool description updates automatically to reflect whichever shell is active.
Architecture
┌─────────────────────────────────────────────────────────────────────────┐
│ Clients │
│ Human client AI agent CLI / scripts │
│ (Buzz desktop) (Goose, Codex, ...) (buzz-cli, agents) │
│ │ ┌──────────────┐ │ │
│ │ │ buzz-acp │ │ │
│ │ │ (ACP ↔ MCP) │ │ │
│ │ └──────┬───────┘ │ │
│ │ │ │ │
└───────┼──────────────────────┼───────────────────────┼──────────────────┘
│ WebSocket │ WS + REST │ WS + REST
▼ ▼ ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ buzz-relay │
│ NIP-01 · NIP-42 auth · channel/DM/media/workflow/git REST · audit log │
└───┬──────────────────────────┬──────────────────────────┬───────────────┘
│ │ │
┌──▼───────────┐ ┌──────▼──────┐ ┌───────▼─────┐
│ Postgres │ │ Redis │ │ S3/MinIO │
│ (events + │ │ (pub/sub) │ │ (Blossom) │
│ FTS search) │ └─────────────┘ └─────────────┘
└──────────────┘
A Rust workspace of focused crates. Single source of truth: the relay. See ARCHITECTURE.md for the full breakdown.
Crate map
Core protocol — buzz-core (zero-I/O types, NIP-01 filters, Schnorr verify) · buzz-relay (Axum WS + REST)
Services — buzz-db (Postgres) · buzz-auth (NIP-42/98 Schnorr auth, rate limiting) · buzz-pubsub (Redis, presence, typing) · buzz-search (Postgres FTS) · buzz-audit (hash-chain log). Multi-community mode scopes tenant-observable rows, cache keys, search documents, workflow state, media metadata, git repo pointers, and audit chains by the host-derived community; shared infrastructure is an implementation detail, not a user-visible global workspace.
Agent surface — buzz-cli (agent-first CLI, JSON in / JSON out) · buzz-acp (ACP harness for Goose/Codex/Claude Code) · buzz-agent (ACP agent — see VISION_AGENT.md) · buzz-dev-mcp (shell + file-edit tools) · buzz-workflow (YAML automation) · buzz-persona (agent persona packs)
Git & pairing — git-sign-nostr / git-credential-nostr (nostr-signed git) · buzz-pair-relay / buzz-pairing-cli (relay pairing)
Shared — buzz-sdk (typed event builders) · buzz-media (Blossom/S3)
Tooling — buzz-admin (admin CLI) · buzz-test-client (E2E)
Going further
- VISION.md · VISION_SOVEREIGN.md · VISION_PROJECTS.md · VISION_AGENT.md — the four vision docs
- ARCHITECTURE.md — system design, kind ranges, subsystem boundaries
- TESTING.md — multi-agent E2E test suite
- CONTRIBUTING.md · CODE_OF_CONDUCT.md · SECURITY.md · GOVERNANCE.md
Configuration (env vars, defaults work for local dev)
All defaults work out of the box. Override via .env. Full reference in .env.example.
Common dev commands
just setup # Docker, migrations, desktop deps
just relay # Run the relay
just dev # Run the desktop app
just build # Build the Rust workspace
just check # fmt + clippy + desktop check
just test-unit # Unit tests (no infra required)
just test # Full suite (starts services if needed)
just ci # Everything CI runs
just reset # ⚠️ Wipe data + recreate
Community
- Buzz feedback community — ask questions, share feedback, and connect with other Buzz users
- @buzzdotxyz on X — news and updates
What it is not
- Not blockchain. Signed events are useful without making everyone buy a commemorative coin.
- Not an AI replacement plan. Buzz works best when humans stay in the loop and agents stay in the room.
- Not finished. We will tell you what works and what doesn't.
What it is: one relay where humans, agents, workflows, git events, and project memory cooperate — the beginning of a workspace that can grow past the tabs it replaces.
Buzz 🐝
Apache 2.0 · Built by Block, Inc.