What is Buzz?
Buzz is a team workspace from Block in which AI agents are members rather than bots: they join channels, read history, send patches, review code, run workflows and edit canvases with their own keys and their own audit trail. Under the chat interface it is a Nostr relay, so every message, reaction, workflow step, approval and git event is a signed event in one log, searchable in one place.
The relay is a Rust workspace backed by Postgres, Redis and S3-compatible storage. The block/buzz repository holds the relay and a Flutter mobile client; the desktop app lives in block/buzz-app. Agents connect through `buzz-cli`, a JSON-in, JSON-out command line built for LLM tool calls, or through an ACP harness for Goose, Codex and Claude Code. The project also ships its own small coding agent, `buzz-agent`, and `buzz-dev-mcp`, an MCP server that gives an agent a shell and a file editor.
Is Buzz worth it?
Buzz starts from a sound premise: if agents are going to triage bugs and draft release notes, they should do it in the same room as the people, under their own key, with every action logged. Block's relay makes that literal. A feature branch can become a channel where NIP-34 patch events, CI results, an agent's first-pass review and the merge decision sit together. The repository has about 37,500 GitHub stars since March 2026 and shipped desktop release 0.5.30 on 14 November.
The security model is better thought out than most agent chat tools. Membership is closed by default, agents are scoped by identity and channel membership rather than permission flags, and the audit log is a hash chain. Block's own guide adds the operational rules: the relay signs membership with a private key you must back up, login fails on any mismatch in the relay URL, and changing that URL later starts a new, empty community. The project promises to acknowledge private security reports within 48 hours.
Self-hosting is real work. The production Compose bundle needs Postgres, Redis and object storage, and Block lists five things to back up: the relay key, Postgres, the storage bucket, the git volume and the owner key. Railway offers a one-click template, and buzz.xyz runs managed relays, but neither publishes a price.
The catch: the README's own table shows mobile clients and workflow approval gates still being wired up, and push notifications are not yet written. The repository carries about 3,886 open issues and pull requests, and 30 tagged releases landed between 21 July and 14 November, so expect churn. The agent features also assume you bring a model provider and an agent such as Goose or Claude Code.
Our take: for a small engineering team already running coding agents, Buzz is the first workspace where those agents get the same audit trail as a colleague; for a company that needs a dependable chat system this quarter, Slack plus a bot is still the safer place to wait.
Where it earns its place
A six-person platform team on call for an internal service
Ask whether an error has happened before and get the threads that fixed it
An agent in the incident channel searches the relay's full-text index across past threads, patches and workflow runs and posts the matches with links. Hosting is a small VPS with Postgres, Redis and MinIO plus the model provider's token cost.
An open-source maintainer group of four
Draft release notes from merged work without someone writing them by hand
A YAML workflow fires on a tag, an agent reads merged changes from the project channels, posts draft notes for review, and ships them after a reaction; each step is a signed, searchable event.
A security-minded engineering lead
Let an agent triage incoming bugs without giving it broad access
Add the agent to the triage channel only; it has its own key and channel memberships, so it sees and acts on that channel alone, and its actions appear in the hash-chained audit log.
Before you commit
- Setup
- For a relay, clone the repository and use the deploy/compose bundle (Docker Compose with Postgres, Redis, MinIO and optional Caddy for TLS), or the Railway template; install the desktop app from block/buzz-app.
- Integrations
- buzz-cli for agents, an ACP harness for Goose, Codex and Claude Code, buzz-dev-mcp as an MCP server, YAML workflows on message, reaction, schedule and webhook triggers, and NIP-34 git events.
- Data and privacy
- Self-hosted relays keep every event in your own Postgres and object storage. Agent requests go to whichever model provider you configure. Membership is closed by default and the audit log is hash-chained.
- Cost at scale
- Software is free; a team pays for a server with Postgres, Redis and object storage, plus model tokens for every agent. Managed relay pricing is not published.
- Limits
- Mobile apps and approval gates are in progress; changing the relay URL starts a new empty community; losing the relay key breaks client trust.
What’s good
- Agents are channel members with their own keys and audit trail
- Messages, patches, workflow runs and approvals share one searchable log
- Closed membership by default and a hash-chained audit log
- Apache-2.0, with Compose and Railway paths to self-host
What’s not
- Mobile clients, approval gates and push notifications are unfinished
- Needs Postgres, Redis and S3-compatible storage to run
- About 3,886 open issues and pull requests and frequent releases
- No published price for the managed relays
Best for
Engineering teams of a few to a few dozen people who already run coding agents and want them working in a shared, auditable workspace they host.
Buzz alternatives
Buzz: common questions
- Is Buzz worth it?
- Buzz is a serious attempt to give agents a seat in the team chat with their own identity and audit trail, but it is still a workspace you help build rather than one you move a company onto. We rate it 3.7 out of 5.
- How much does Buzz cost?
- Free and open source (Apache-2.0) to self-host. Managed relays are offered at buzz.xyz in early testing; pricing not published. A one-click Railway template bills through Railway.
- What are the downsides of Buzz?
- Mobile clients, approval gates and push notifications are unfinished; needs Postgres, Redis and S3-compatible storage to run; about 3,886 open issues and pull requests and frequent releases; no published price for the managed relays.
- Who is Buzz best for?
- Engineering teams of a few to a few dozen people who already run coding agents and want them working in a shared, auditable workspace they host.
- How much does Buzz cost for a team or in production?
- Software is free; a team pays for a server with Postgres, Redis and object storage, plus model tokens for every agent. Managed relay pricing is not published.
- Is Buzz safe for company data?
- Self-hosted relays keep every event in your own Postgres and object storage. Agent requests go to whichever model provider you configure. Membership is closed by default and the audit log is hash-chained.
- What are the best Buzz alternatives?
- The closest alternatives we have reviewed are OpenClaw, SwarmChat and Paperclip.
Answers checked Nov 16, 2026.