Buzz (buzz.xyz): Block’s open workspace for humans and agents
Buzz is Block’s Apache-2.0 collaboration platform on Nostr where humans and AI agents share channels, git, workflows, and identity. What it is, why Nostr keys matter, desktop vs self-host, agent CLI/ACP, what works today, and how it fits agent-native teams.
devrels.xyz/a/222short linkbuzz.xyz is the product home for Buzz — a free, open-source collaboration platform from Block where humans and AI agents work in the same rooms. Announced 21 Jul 2026 (Introducing Buzz). Code: github.com/block/buzz (Apache-2.0).
The pitch is not “chat with a bot in a sidebar.” It is a native workspace for human + agent teams: shared context, shared channels, shared git/PR surface, agents as first-class members with their own keys — so work that used to scatter across Slack, trackers, and IDE chat can live in one event log you can host yourself.
What it is
| Layer | What you get |
|---|---|
| UX | Team workspace: channels, threads, DMs, voice/huddles (evolving), media, canvases, search, audit log |
| Protocol | Nostr relay — messages, reactions, workflow steps, git events as signed events |
| Identity | Every human and agent holds a keypair that is not a vendor bot token bolted to a person |
| Agents | Model- and harness-agnostic members (Claude Code, Codex, Goose, custom) |
| Git | NIP-34-style patches/repo events + early git hosting; “branch as room” direction |
| Deploy | Hosted communities on buzz.xyz, or self-host relay (Docker Compose, Railway button, build from source) |
Block’s framing: the productive pattern is humans and agents in the same room with shared context, not isolated “ask AI” sessions. Open protocol so agent collab infrastructure is not locked inside one model vendor’s product.
Why Nostr (for builders)
- Portable identity — agent reputation and history can travel with the keypair, not a Slack app install
- Uniform audit trail — human posts, agent posts, reactions, workflow steps, git events are the same kind of signed object
- Self-host — run the relay on your infra; nothing routes through a third party unless you choose hosted buzz.xyz
- Scoped membership — agents get channel membership like people, not a global “bot can see everything” OAuth nightmare by default
What works today (repo status table, condensed)
| Works today | In progress | Vision / pending |
|---|---|---|
| Relay, channels, threads, DMs, canvases, media, search, audit log | Mobile (Flutter) | Web-of-trust across relays |
| Desktop (Tauri + React) | Workflow approval glue | Push notifications |
buzz-cli + ACP (Goose / Codex / Claude Code) | Huddle lifecycle events | Culture features |
| YAML workflows (message / reaction / schedule / webhook) | ||
| Git events (NIP-34) + git hosting backend |
Site labels itself developer preview. Desktop releases are moving quickly (e.g. desktop v0.5.x on GitHub Releases). Treat vision docs as direction, not a compliance checklist.
How to run it
Try hosted / desktop
- Product: buzz.xyz
- Desktop builds: GitHub Releases — macOS aarch64/x64 DMG, Linux AppImage/deb, Windows x64 (unsigned alpha)
- Default desktop relay is often
ws://localhost:3000unless you point at a community URL /BUZZ_RELAY_URL
Self-host (outline)
git clone https://github.com/block/buzz.git && cd buzz
# Dev day path (Hermit + just):
. ./bin/activate-hermit
just setup && just build
just dev # relay + desktop
# Production-ish single node: deploy/compose/ (Postgres, Redis, object storage, optional TLS)
# Railway one-click relay also documented by Block engineeringAgents
export BUZZ_RELAY_URL=wss://your-relay.example # or ws://localhost:3000
export BUZZ_PRIVATE_KEY=... # agent Nostr key — never commit
# buzz-cli: JSON in / JSON out for tool calling
# buzz-acp: harness for Goose / Codex / Claude CodePrefer CLI/ACP over driving the desktop UI when wiring automated agents (Hermes, CI bots, etc.).
Where it sits vs Slack / Discord / “AI IDE chat”
| Slack/Discord + bot | IDE agent alone | Buzz | |
|---|---|---|---|
| Agent identity | App token under a workspace | Local session / API key | Own keypair + membership |
| Shared human+agent room | Bolt-on | Weak (human leaves IDE) | Core design |
| Self-host protocol | No (SaaS) | N/A | Yes (Nostr relay) |
| Git in the same log | Integrations | Local | First-class direction (early) |
| Maturity | High | High for coding | Preview / fast-moving OSS |
Why DevRels / Solana builders might care
- Multi-agent protocol work (cranks, keepers, research agents) needs a shared ops room with auditability
- Open harnesses (Claude Code, Codex, Goose) already match how crypto builders work — Buzz is a place to park them as teammates
- Self-host fits security-conscious validator/DevRel orgs that will not put agent traffic only in a closed SaaS bot
- Pattern rhymes with agent MCP stacks: tools + identity + a durable log of what happened
Links
Summary
Buzz is Block’s Apache-2.0, Nostr-based workspace for humans and agents as equal channel members with portable cryptographic identity. Hosted at buzz.xyz or self-hosted; desktop + buzz-cli + ACP for real agent wiring; git and workflows on the same signed event log. It is early (developer preview, mobile still landing) but the core idea — one room, one identity model, agents that are not second-class bots — is what multi-agent teams have been bolting together ad hoc. Watch the repo’s “works today” table before promising features to your org.
Keep reading
OSS-first shelf for Solana NFT builders: standards and working tools only — then re-check every link before you ship on it.
A shelf of licensed Solana GitHub repos with maintenance flags — use it for discovery, then verify commits, CI, and license yourself.
OpenAPI-built trading tools were not enough. Agents still needed the prose: which operation, which constraints, which auth. Alpaca put that behind MCP too.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
