Block Buzz: The Self-Hosted Workspace Where AI Agents Are Teammates, Not Bots
> Block Buzz is an open-source, self-hosted Nostr workspace where humans, AI agents, Git events and approvals share one signed, searchable event log.
🎧 Listen — ~5 min
Ready · Block Buzz: The Self-Hosted Work
Block's Buzz is an open-source, self-hosted collaboration workspace built around a Nostr relay—not another chat app with an AI sidebar. Its core idea is unusually direct: humans, agents, workflows, reactions, approvals and Git events should share one signed, searchable event log.
That makes Buzz worth watching for teams building with coding agents. It does not replace a mature Slack + GitHub + CI estate overnight, and several ambitious features remain in progress. But its architecture tackles a real weakness of today's agent stack: the context for a decision is fragmented across chat, tickets, pull requests, terminal transcripts and automation logs.
Courtesy: Block, Inc. / Buzz GitHub repository. Screenshot from the project's public documentation, accessed July 29, 2026.
What is Block Buzz?
Buzz is an Apache-2.0 licensed Rust workspace from Block. In its default self-hosted shape, a relay serves one community. The desktop client, workflows and command-line tools connect to that relay; the relay stores signed Nostr events and indexes them for search.
The product currently documents channels, threads, direct messages, canvases, media comments, search, audit logging, Git events, YAML workflows, a desktop app, buzz-cli, and an ACP-facing agent harness. It also has an explicit roadmap boundary: mobile clients, approval-gate wiring and huddle lifecycle work are marked as in progress, while reputation and push-notification ideas are still aspirations.
The important distinction is architectural. A message and a workflow approval are not merely notifications emitted by different services. Buzz aims to make them records in the same log, signed under the same identity model.
Why it matters for AI-agent teams
Most AI agents are bolted onto a workplace as bots. They receive a token, post into selected channels and leave their operational trail in another dashboard. Buzz instead gives an agent its own keypair, memberships and history—much closer to how a human teammate participates.
That can make a project room useful as durable operational memory. An agent can investigate an incident, cite earlier threads, attach a patch or workflow result, and leave the evidence beside the human discussion and final approval. The benefit is not that an agent becomes autonomous; it is that a human can reconstruct what happened without spelunking across five products.
Courtesy: Block, Inc. / Buzz GitHub repository. Screenshot from the project's public documentation, accessed July 29, 2026.
Buzz vs. a conventional collaboration stack
| Dimension | Buzz | Typical split stack |
|---|---|---|
| System of record | Signed relay event log | Chat, Git, CI and agent logs separate |
| Identity | Nostr keys for people and processes | Vendor accounts, tokens and bot users |
| Self-hosting | Supported relay / Compose path | Varies by product |
| Agent role | First-class workspace participant | Usually integration or service account |
| Git + collaboration context | Git events alongside room history | Cross-linked across tools |
| Audit trail | Signed, searchable events | Distributed across vendor records |
The chart describes the design difference, not a claim that Buzz has every enterprise feature of Slack, GitHub, Jira, CI providers or dedicated agent platforms. Those products are broad, mature ecosystems. Buzz's wager is that a shared event substrate can make collaboration and agent work more inspectable.
The technical stack: Nostr, Rust, ACP and MCP
Buzz uses Nostr event semantics for its relay and identity model. The relay advertises NIP-01 event handling and NIP-42/NIP-98 authentication, with Postgres for events and full-text search, Redis for pub/sub and presence, and S3-compatible object storage for media. The production deployment documentation uses Docker Compose with Postgres, Redis, MinIO and optional Caddy/TLS.
For agents, the project separates two concerns:
buzz-agentspeaks the Agent Client Protocol (ACP) over stdio and can manage concurrent sessions.buzz-dev-mcpis an MCP server that exposes controlled development tools such as shell and file editing.
That separation matters. ACP lets different clients talk to an agent through a standard protocol; MCP lets that agent use tools through another standard protocol. The Buzz docs describe per-session MCP-server instances and bounded process/output behaviour, but teams should still treat tool access as a security boundary: use least-privilege credentials, isolate repositories, restrict network access and require human approval for merges, deployments, secrets and destructive actions.
What works today—and what to verify before adopting it
Buzz's README lists a runnable local path: Docker, Hermit (or the stated Rust/Node/pnpm tooling), just setup, then just dev. It also provides packaged desktop releases for macOS, Linux and Windows. The latest GitHub release at the time of writing is v0.5.0, published July 28, 2026.
For a serious team, run a small pilot instead of planning a wholesale migration:
- Stand up a non-production relay on a disposable environment.
- Create one engineering community and one limited-scope agent identity.
- Connect a read-only repository and one MCP server with no production credentials.
- Test search, retention, backup/restore, audit export, user offboarding and incident review.
- Add approvals before any agent can write to Git, trigger a deployment or touch customer data.
The model is promising, but it shifts responsibility to the operator. Self-hosting means owning patching, backups, key management, TLS, observability, abuse controls and retention policy. Signed events improve traceability; they do not automatically solve access control, compliance or safe automation.
The verdict
Buzz is one of the more coherent attempts to design an agent-native workspace from the substrate upward. It is especially interesting for technical teams that want self-hosting, auditable agent participation and a tighter link between conversation, code and workflow evidence.
For now, treat it as an early but substantial open-source platform: excellent for an internal pilot, not a casual replacement claim for your entire collaboration stack. If Block keeps the protocol-first design while hardening operational controls and approval flows, Buzz could become a serious alternative to the fragmented "chat plus bots plus tabs" model.
Sources
- Block Buzz GitHub repository and README
- Buzz architecture documentation
- Buzz agent vision and ACP/MCP design
- Buzz releases
Related guides
Keep reading
Related reading
⚡ Daily AI Model Drop — Get Kimi K3 benchmarks before Twitter
Join 2,400+ AI engineers. 1 email/day, no spam, unsubscribe anytime