Jack Dorsey's Buzz Is What Happens When a CEO Actually Dogfoods His Own Thesis

Jack Dorsey launched Buzz yesterday. Block's new open-source workspace combines team chat, AI agents, and a built-in Git forge into one self-hostable platform built on signed Nostr events. It's ambitious, unfinished, and exactly the kind of product you'd expect from someone who's been saying AI should reshape how companies organize — not just how they autocomplete emails.

Buzz is not another Slack clone with an LLM bolted on. It's a rethinking of what a development workspace looks like when humans and AI agents share the same identity system, the same audit trail, and the same cryptographic key pairs. Every message, reaction, workflow step, code commit, and approval is a signed Nostr event. Agents don't sit in channels as bot users — they participate as members with their own key pairs, channel memberships, and access controls.

I've been running servers long enough to be skeptical of press releases dressed as products. But Buzz is real code — 1,767 commits on GitHub, Apache 2.0 licensed, desktop builds for macOS, Windows, and Linux. Version 0.4.21 shipped yesterday with fixes covering agent controls, authentication, and workspace onboarding. The commit history shows real engineering velocity from a real team.

One Relay to Rule Them All

The architecture is worth understanding because it reveals what Buzz actually is versus what the marketing says. Buzz is built around a self-hostable Nostr relay. Every workspace — whether you run it yourself or use a hosted operator — routes all reads and writes through a single relay. The relay authenticates users, verifies signatures, stores events, and distributes updates.

Dorsey described Buzz as "decentralized and self-sovereign" in his announcement on X, which received over 8,600 likes. But the architecture document draws a more precise boundary. There is no peer-to-peer event exchange, no gossip layer, no replication between relays. Within each community, the relay is the authoritative server.

The decentralization comes from deployment and ownership, not from protocol topology. You can run your own relay, keep your own data, and use portable Nostr key pairs. You are not dependent on a single hosted service. But within your workspace, the relay is still a single point of failure. Self-hosting gives you control over infrastructure and data location. It also transfers full responsibility for availability, backups, security, and upgrades.

That distinction matters. The signed event model provides attribution and an audit trail. It does not eliminate the operational risks of running the server that holds your entire workspace.

Agents as First-Class Citizens

This is where Buzz stops being a Slack alternative and starts being something different. Buzz gives AI agents the same identity structure as human employees. They get key pairs. They get channel memberships. They can search prior discussions, open repositories, submit patches, review code, run workflows, edit shared canvases, and create their own channels.

Block has built harnesses for Goose, Codex, and Claude Code, keeping the underlying model choice separate from the workspace itself. If your team prefers Claude for code review and GPT for documentation, you can wire both in. The workspace doesn't care which model backs which agent.

This is the piece that actually matters for infrastructure people. Most AI integrations in existing tools treat agents as chat bots — they sit in a channel, wait for an @mention, and respond in a thread. Buzz treats them as participants with persistent identity, persistent access, and persistent audit trails. An agent that opens a PR, submits a patch, and triggers a CI workflow leaves the same signed event trail as the human who approves the merge.

That's not a feature list. That's a fundamentally different operating model for how software gets built.

The Built-In Git Forge

Buzz includes a software forge using standard Git Smart HTTP, and the integration goes beyond posting commit notifications into a channel. The project specification describes a workflow where a feature branch becomes its own channel. Patches, CI results, review comments, and the merge decision are all preserved in the same signed event record. Repositories, discussions, and workflow history share one search index.

If you've ever maintained a Slack workspace, a GitHub org, a CI system, and a documentation wiki — and tried to give an AI agent useful context across all four — you understand why this consolidation is compelling. The integration tax on modern development stacks is enormous. Every tool adds its own auth, its own API surface, its own permission model, and its own siloed search. Buzz collapses those surfaces into one event system with one identity layer.

The currently working feature set includes channels, threads, direct messages, shared canvases, media search, an audit log, a desktop application, and YAML-based workflows. That's substantial for a v0.4 release.

What This Means: The Operating Model Shift

Dorsey has been building toward this for a while. In an essay with Sequoia Capital's Roelof Botha, he argued that AI should change how organizations coordinate rather than serve only as a productivity add-on. Buzz is the infrastructure layer for that thesis — a workspace designed from the ground up for mixed human-agent teams.

The implications for anyone running infrastructure are direct. If Buzz or something like it becomes the standard workspace model, the operational requirements change. You're not just running a chat server and a Git server and a CI server anymore. You're running a relay that authenticates both human and machine identities, maintains a cryptographic audit trail for every action, and supports agents that operate autonomously within your infrastructure.

That changes your monitoring, your backup strategy, your security incident response, and your capacity planning. An agent that runs a workflow at 3 AM and commits a patch leaves the same forensic evidence as a human developer. That's good for accountability. It also means your relay uptime is your team's productivity.

There is also a real competitive landscape forming here. Paradigm CTO Georgios Konstantopoulos recently open-sourced Centaur, a self-hosted "virtual employee" that runs inside Slack or via API. The emerging pattern is clear: self-hosted, open-source workspaces where agents operate alongside humans with full identity and access control. The vendors who own the identity layer will own the developer workflow.

The Early-Stage Reality Check

Buzz's own documentation calls it unfinished. Mobile clients are still in development. Push notifications are pending. Workflow approval gates have database, API, and interface components without a completed execution path. The desktop build shipped yesterday at version 0.4.21 — early alpha territory by any measure.

Block has not published any adoption figures, pricing, or external customer data. The only documented deployment is Block's own internal instance, configured for Block's relay and agent provider. Buzz is, at this moment, an open-source build and an invitation to contribute — not a product you should migrate your team to next week.

The scope is also its risk. Buzz replaces portions of chat, code hosting, workflow automation, project search, and agent orchestration with one event system. That's a bet on consolidation over best-of-breed. If the relay goes down, your chat, your code, your CI, and your agent coordination all go down together. Teams that adopt Buzz are trading integration complexity for operational concentration.

What Comes Next

Buzz makes the most sense as a bet on where development workspaces are heading, not as a replacement for what you're running today. The combination of signed Nostr events, self-hosted infrastructure, and agent-native identity is the trajectory. Whether Buzz is the vehicle or the prototype that inspires the real product is an open question.

For infrastructure operators, the signal is clear. The next generation of development tools will assume agents are first-class participants. Your monitoring, your access controls, your backup strategy, and your incident response need to account for machine identities that operate autonomously on your infrastructure. Start planning for that now, because the open-source tooling is already shipping.

The Buzz repository is at github.com/block/buzz under Apache 2.0. Desktop builds are available for all three platforms. Go spin up a relay, run through the onboarding, and see what a Nostr-native workspace actually feels like. The early stage is exactly when you want to understand the architecture — before your team depends on it.

— Allan Ali, Sylt.ing

===SUMMARY===Jack Dorsey's Block launched Buzz, an open-source workspace combining team chat, AI agents, and Git hosting on a self-hostable Nostr relay. Built with signed cryptographic events and agent-native identity, Buzz treats AI agents as first-class participants with their own key pairs and audit trails. Early stage but signals where development infrastructure is heading.