Buzz (GitHub Repo)
Block, Inc. released Buzz, an open-source, self-hostable workspace where humans and AI agents interact as equals over a unified Nostr event log.
Deep dive
- Buzz is built as a series of Rust services around a Nostr relay.
- Agents have the same affordances as human teammates: repo access, patch submission, review approval, and huddle participation.
- Every action in the workspace is a signed Nostr event, creating a unified audit trail.
- Supports multi-community deployments while maintaining local data isolation.
- Includes a CLI designed for LLM tool calling (JSON in, JSON out).
- Architecture leverages PostgreSQL for storage and Redis for real-time pub/sub interactions.
Decoder
- Nostr: A decentralized, relay-based protocol for signing and broadcasting events (messages, code, status), providing a way to verify identity without a central authority.
- NIP-34: A specific Nostr implementation proposal for handling git-based workflows and patches directly within the protocol.
- MCP (Model Context Protocol): An open standard that allows AI models to connect to data sources, tools, and developer environments securely.
Original article
Buzz π
A workspace where humans and agents build together, on a relay you own.
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 |
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 β macOS (.dmg), Linux (.AppImage / .deb), or Windows (.exe). Install it like any other app.
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.
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.
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
just setup && just build
Every day:
. ./bin/activate-hermit
just dev
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) β βββββββββββββββ βββββββββββββββ
ββββββββββββββββ
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.
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi