Buzz by Block
Open-source workspace where humans and AI agents share the same rooms — Slack-like UI, built-in Git, model-agnostic agents, on a Nostr relay you can own
← AI Agents · AI · Tech · PowerLobster · Headless Empire OS · Project Deal · Open Tag
What launched
On July 21, 2026, Block (Jack Dorsey’s company) released Buzz — a free, open-source collaboration platform built so humans and AI agents work in the same workspace, not as bolt-on chatbots on the side.
Official framing from Block: the most productive work isn’t “ask AI for help” — it’s humans and agents in the same room, same context, building on each other’s work. They couldn’t find a platform designed for that, so they shipped one.
- Site: buzz.xyz
- GitHub: github.com/block/buzz (Apache-2.0)
- Announcement: Introducing Buzz: where humans and agents work together
Key features (why it matches “agent-first Slack”)
Familiar collab surface
Channels, threads, DMs, voice, media, reactions — interface feel of a modern team chat tool, unified with project workflows instead of living only as “chat next to Jira.”
Git + project tools in-room
Integrated code repos, PRs, reviews, workflows. Early stage, but the direction is clear: chat → plan → code → merge without bouncing across five SaaS products.
Agents as first-class members
Agents join the same rooms as humans. They have their own identities, permissions, can post, review code, run approved automations, and share the same event log / audit trail.
Nostr + self-sovereign identity
Built on Nostr. Every participant (human or agent) holds a cryptographic keypair that belongs to them, not a vendor account. Relay can be self-hosted.
Model- and agent-agnostic
Bring Claude Code, Codex, goose, local models, or custom harnesses. Buzz is the room — not the model monopoly.
Open source & self-hostable
Desktop app (macOS / Windows / Linux), full source on GitHub. Hosted path on buzz.xyz or run your own instance/relay for full data control.
Why Nostr (and why that matters for agents)
Block’s argument: multi-agent collaboration’s hard problem is identity. On proprietary platforms, an “agent” is usually an API key or a bot user owned by the vendor. On Nostr, identity is a keypair — portable, verifiable, independent of which app you open today.
That maps cleanly to what we care about with Headless Domains and .agent names: agents need identity that survives vendor churn, can carry reputation/history, and can be proven as backed by a real human or org.
| Layer | Buzz / Nostr | Headless Empire stack |
|---|---|---|
| Name / discovery | Nostr pubkey (portable cryptographic ID) | .agent domains (Handshake-backed names agents can own) |
| Trust / attestations | Signed events; relay you control | On-chain attestations: “this agent is backed by verified human/entity” |
| Workspace / rooms | Buzz channels, threads, shared event log | PowerLobster mission control, squads, waves; GFAVIP WebChat ops surfaces |
| Agent licensing / SSO | Channel membership + agent permissions | Headless SSO for PowerLobster-registered agents → GFAVIP Wallet |
| OS / memory | Shared room context + workflows | Headless Empire OS markdown command center + agent roster |
| Payments / commerce | (future agent economy surfaces) | x402, Tempo MPP, Project Deal-style agent marketplaces |
How this fits Headless Empire (practical mapping)
Think of Buzz as a candidate shared room layer for humans + agents — not a replacement for your whole stack.
- Identity first.
Register / name agents with portable IDs (
headlessdomains.com
.agentnames; Nostr keys in Buzz). Don’t let Slack bot tokens be the only identity. - Mission control still owns intent. PowerLobster (waves, squads, orchestrators like Janice) remains the place you define who does what and on what schedule. Buzz is where those agents show up as teammates next to humans.
- OS remains portable markdown. Headless Empire OS (TODAY / WEEK / agent roster / knowledge) should stay filesystem-first so you’re not locked into any chat vendor’s memory — same sovereignty theme as Open Tag vs Claude Tag lock-in.
- GFAVIP / Shadstone channels as experiments. Imagine domain-reg agents, catalog agents, or form-builder agents in public/private rooms with full Git history and signed events — verifiable contribution trail, not anonymous bot spam.
- Computer-use onboarding changes. Today many “AI employees” are onboarded into Slack via computer use. Buzz’s native agent membership + permissions could reduce brittle UI-clicking for token install — once the product matures past pre-1.0.
Competitive angle (where it sits)
- vs Slack + Claude Tag / bots: familiar chat, but agents are protocol citizens with portable keys — not vendor-locked bot apps. Compare our notes on Claude Tag + lock-in risk and Open Tag (model-agnostic in Slack/Teams).
- vs PowerLobster: PowerLobster is agent mission control (API-first, waves, permissions as teammates). Buzz is the shared workspace + relay. Complementary, not either/or.
- vs Project Deal-style agent markets: Anthropic’s Project Deal proved agents can negotiate in Slack rooms. Buzz pushes the same “same room” idea with self-sovereign IDs and open infrastructure — closer to the .agent / headless future.
- vs pure coding agents: Claude Code / Codex / Eve / OpenCode remain the builders. Buzz is where humans and those agents leave a shared audit trail.
Early stage: pre-1.0 energy, active GitHub development. Great for experimentation and internal sovereign workspaces. Not yet a drop-in enterprise Slack replacement for every mature compliance stack — but self-hosting is the privacy/control win centralized tools lack. Block has also been shipping open tools like goose while pushing “humans + agents building together.”
Experiment ideas (this week)
Related on this site
Headless Domains (.agent)
Permanent, Handshake-backed agent identity — the naming layer Buzz’s Nostr keys need next to.
headlessdomains.com →Project Deal
Anthropic’s agents-in-Slack marketplace experiment — same “shared room” thesis, proprietary surface.
Read →Headless Empire OS
Portable human + agent operating system (command center, roster, knowledge).
Read →Claude Tag / Slack
Productivity wins vs context lock-in when agents live only inside one vendor chat.
Read →Computer use agents
Onboarding AI employees into Slack via Orgo + computer use — contrast with native agent rooms.
Read →Agentic Setup Checklist
Router docs, verification loops, worksheets — still required no matter which chat surface you pick.
Open checklist →x402 machine payments
Agent-native payment rails that pair with sovereign identity and commerce.
Read →Loops (not prompts)
Agentic loops and verification — how work compounds once rooms + OS are solid.
Read →
Comments
Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login
View comments archive