All articles
buzzblocknostragentscollaborationopen-sourcedevtoolsbuilders

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 link

buzz.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

Product shape
LayerWhat you get
UXTeam workspace: channels, threads, DMs, voice/huddles (evolving), media, canvases, search, audit log
ProtocolNostr relay — messages, reactions, workflow steps, git events as signed events
IdentityEvery human and agent holds a keypair that is not a vendor bot token bolted to a person
AgentsModel- and harness-agnostic members (Claude Code, Codex, Goose, custom)
GitNIP-34-style patches/repo events + early git hosting; “branch as room” direction
DeployHosted 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)

From block/buzz README
Works todayIn progressVision / pending
Relay, channels, threads, DMs, canvases, media, search, audit logMobile (Flutter)Web-of-trust across relays
Desktop (Tauri + React)Workflow approval gluePush notifications
buzz-cli + ACP (Goose / Codex / Claude Code)Huddle lifecycle eventsCulture 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

  1. Product: buzz.xyz
  2. Desktop builds: GitHub Releases — macOS aarch64/x64 DMG, Linux AppImage/deb, Windows x64 (unsigned alpha)
  3. Default desktop relay is often ws://localhost:3000 unless you point at a community URL / BUZZ_RELAY_URL

Self-host (outline)

bash
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 engineering

Agents

bash
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 Code

Prefer CLI/ACP over driving the desktop UI when wiring automated agents (Hermes, CI bots, etc.).

Where it sits vs Slack / Discord / “AI IDE chat”

Rough comparison
Slack/Discord + botIDE agent aloneBuzz
Agent identityApp token under a workspaceLocal session / API keyOwn keypair + membership
Shared human+agent roomBolt-onWeak (human leaves IDE)Core design
Self-host protocolNo (SaaS)N/AYes (Nostr relay)
Git in the same logIntegrationsLocalFirst-class direction (early)
MaturityHighHigh for codingPreview / 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

Get new articles in your inbox

Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.

Buzz (buzz.xyz): Block’s open workspace for humans and agents | devrels.xyz