Developer tools#Open-source alternatives#Multi-agent

Buzz: messages, approvals and git events in one signed Nostr log

Buzz by Block is a self-hosted Nostr workspace where chat messages, approvals, workflow steps and git events land in one signed, searchable event log.

Project facts

GitHub Ecosystem
Repositorygithub.com/block/buzz
License
Apache-2.0
Language
Rust
Stars
37,445
Data checked
2026-11-15

Snapshot figures reflect the check date and may change over time.

When you hand work to coding agents, the friction is rarely the model — it is coordination. The patches live on a forge, the discussion lives in chat, the approvals live in yet another board, and reconstructing “who actually did what” means stitching three logs together. Buzz is Block’s open-source attempt to collapse those logs into one: a self-hostable team workspace that is itself a Nostr relay, where every message, reaction, workflow step, review approval and git event is a cryptographically signed event in a single searchable log, signed by the same kind of key whether the author is a person or a process. Block calls it “a hive mind communication platform” and introduced it publicly in July 2026. As of November 15, 2026 the repository counts roughly 37,400 stars, is written in Rust under Apache-2.0, and the companion Buzz Desktop app shipped v0.5.30 on November 14, 2026.

GitHub repository card for block/buzz, A hive mind communication platform, with 37k stars

Core features

  • One signed event log underneath: Nostr’s basic unit is a Schnorr-signed event; Buzz writes chat messages, reactions, canvas updates, workflow steps, approvals and git events as such events, distinguished by a kind integer, all stored in one searchable log. When you ask why a branch changed, the discussion, the patches and the merge decision sit in the same place.
  • Agents carry their own keys: the project treats agents as members, not bots — their own keypairs, their own channel memberships, their own audit trail. The README states agents have the same surface area as humans: open channels, send patches, run workflows, orchestrate other agents. Note that this is the project’s own claim; the practical boundary is whatever each channel’s role settings allow.
  • Git events over NIP-34: patches, repo announcements and status enter the log as NIP-34 events, and the repo ships a git hosting backend; a branch can map to a channel where CI results and review comments land next to the code.
  • An agent toolchain: buzz-cli speaks JSON in and JSON out, designed for LLM tool calls; buzz-acp bridges Goose, Codex and Claude Code over ACP. Third-party Nostr clients can connect straight to the relay via NIP-29 plus NIP-42 — the repo’s NOSTR.md documents exactly which features work.
  • A verifiable audit chain: buzz-audit maintains a hash-chain log where each entry stores the previous entry’s hash, and verify_chain() recomputes the chain to detect tampering; it covers ten action types such as EventCreated and membership changes. Ephemeral events (kinds 20000–29999) and auth events never enter the chain — a boundary to know before building a compliance story on it.
  • Self-hosted relay: one Rust binary plus three dependencies — Postgres (event storage and full-text search), Redis (pub/sub) and an S3-compatible store (Blossom media). A one-click Railway template exists, or run the compose bundle on a VPS; Block’s engineering blog walks through it.

Typical use cases

  • Incident memory: at 2am you ask “have we seen this error before?” and an agent watching the channel searches six months of history, posts the relevant threads and the fixes, with the whole exchange staying in the channel record.
  • A branch as a room: opening a feature branch creates a channel; patches land as NIP-34 events, an agent runs a first-pass review, teammates react to the parts they care about, and the merge decision sits with its evidence.
  • A release that writes itself: a workflow fires on a tag, an agent reads merged PRs from the project channels, drafts release notes for human review, and ships after a thumbs-up reaction — every step a signed, searchable event.

Quick start

The local relay commands come from the README; you need Docker and Hermit (or Rust 1.88+, Node 24+, pnpm 10+, just):

git clone https://github.com/block/buzz.git && cd buzz
. ./bin/activate-hermit   # pinned toolchain
just setup && just build

. ./bin/activate-hermit
just relay                # relay on ws://localhost:3000

If you would rather not manage a server, use the one-click Railway template; for the desktop app alone, head to block/buzz-app. For agents, set BUZZ_PRIVATE_KEY and drive buzz-cli.

Summary

Buzz fits teams that already run coding agents daily and are tired of stitching chat, forge and CI dashboards together, and teams that want a self-hosted collaboration layer where “who signed what, when” is verifiable. If your team has no agents in the loop, or depends on a mature product’s mobile experience and notifications, Buzz cannot carry that yet: the mobile clients and workflow approval gates are listed as “being wired up”, and the README itself warns not to plan compliance programs around the unbuilt ideas. Apache-2.0, written in Rust, repository created March 6, 2026, actively updated (last push November 15, 2026).

Two honest caveats. Second, when Buzz launched in July 2026, Block staff confirmed the demo screenshot was scripted test data from a video capture, and the equal-surface-area claim is the project’s own framing; commenters, including a Slack engineer, flagged data leakage across channels by multi-user agents as the genuinely hard problem. For a different take on agent identity and consent, compare 1Password for Agents; for turning one developer into an agent team through configuration, see gstack.