Jack Dorsey has launched Buzz — an open-source workspace that puts human employees and AI agents in the same chat, on the same cryptographic identity system, behind the same audit trail. The pitch is simple: one workspace for humans and agents, built on Nostr, self-hostable, replacing Slack and GitHub with a single protocol. Block is the first customer, and Dorsey is betting his own company’s workflow on it.
The announcement, made on X on July 21, comes with a public GitHub repository licensed under Apache 2.0, desktop apps for macOS, Windows, and Linux, and an architecture document that’s surprisingly honest about what works and what doesn’t. Buzz is version 0.4.21. It is, by Block’s own admission, unfinished.
What is Nostr? It’s a decentralized protocol where every message, reaction, and event is a cryptographically signed note relayed through servers. Originally designed for social media, it gives every user a cryptographic key pair — no central account database. Buzz repurposes this for the workplace: every message, code event, workflow step, and agent action becomes a signed, auditable event.
🔍 THE BOTTOM LINE
Dorsey is betting that the future of work isn’t humans using AI tools — it’s humans and AI agents sharing the same workspace as equals. Buzz gives both the same identity, the same channels, and the same audit trail. It’s open-source, self-hostable, and built on Nostr. It’s also version 0.4, missing mobile, and competing against Slack, GitHub, and a dozen agent orchestration startups. But if Dorsey’s thesis holds, the workplace of 2027 won’t have a separate “AI tab” — agents will just be colleagues.
One Identity for Humans and Agents
Buzz is built around a self-hostable Nostr relay. Every message, reaction, workflow step, code event, and approval is stored as a cryptographically signed event. Human employees and AI agents receive the same basic identity structure — their own key pairs, channel memberships, and audit trails.
That design decision is the interesting part. Agents in Buzz aren’t chat bots that sit in a side panel. They’re members. According to Block’s documentation, agents can search prior discussions, open repositories, submit patches, review code, run workflows, edit shared canvases, and create channels. Buzz includes an agent-oriented command-line interface and harnesses for Goose, Codex, and Claude Code — keeping the underlying model choice separate from the workspace.
The Git integration goes beyond posting repository notifications into chat. The project specification describes a built-in software forge using standard Git Smart HTTP. A feature branch becomes its own channel, with patches, CI results, review comments, and the merge decision preserved in the same record. Repositories, discussions, and workflow history share one search index.
What’s Actually Working Today
The currently working feature set includes channels, threads, direct messages, shared canvases, media, search, an audit log, a desktop application, and YAML-based workflows. Packaged builds are available for macOS, Windows, and Linux.
What’s not working: mobile clients remain in development, push notifications are pending, and workflow approval gates have database, API, and interface components without a completed execution path. The latest desktop release, version 0.4.21, shipped on July 21 with fixes covering agent controls, authentication, and workspace onboarding.
Block’s own documentation repeatedly labels the product unfinished. This is refreshing honesty from a company that could have launched with a marketing blitz.
Decentralized in Ownership, Not in Architecture
Dorsey described Buzz as “decentralized and self-sovereign,” but Block’s architecture document draws a more specific boundary. Buzz currently has no peer-to-peer event exchange, no gossip layer, no replication between relays. All reads and writes pass through a single relay, which authenticates users, verifies signatures, stores events, and distributes updates.
The decentralization is in deployment and ownership. An organization can run its own relay, retain its domain and data, and use portable Nostr key pairs instead of depending on a hosted service. Within each community, however, the relay is the authoritative server.
This matters for teams evaluating Buzz as a Slack or GitHub substitute. Self-hosting gives control over infrastructure and data location, but it also transfers responsibility for availability, backups, security, and upgrades. The signed event model provides attribution and audit trail; it does not remove the operational risks of running a server.
Why Dorsey Is Doing This
Buzz fits the operating model Dorsey has been building inside Block. In an essay with Sequoia Capital’s Roelof Botha, Dorsey argued that AI should change how organizations coordinate — not just serve as a productivity add-on bolted onto existing tools. Buzz supplies an infrastructure layer for that thesis.
Dorsey’s preference for open protocols is well-documented. He pushed Twitter toward open standards before leaving, championed Nostr as a decentralized social protocol, and has consistently argued that companies should own their own infrastructure rather than renting it from a handful of platforms. Buzz extends that philosophy to the workplace.
The move also reduces Block’s dependence on Slack and GitHub — two platforms that charge per-seat and control the data. If agents count as seats, and every team has five to ten agents running, those bills scale fast. Buzz eliminates that cost structure for Block, and for any company that self-hosts.
The Competition
Buzz is entering a crowded space. Slack has been adding AI features. Microsoft Teams integrates with Copilot. GitHub is the default code host for most of the industry. And a wave of agent orchestration startups — LangChain, CrewAI, AutoGen — are building the agent management layer separately.
Dorsey’s bet is that combining all of these into one protocol-native workspace is better than bolting agents onto existing tools. The argument has merit: agent context is fragmented when chat lives in Slack, code lives in GitHub, and agent orchestration lives in a separate platform. One workspace with one search index and one audit trail could reduce that fragmentation.
But combining surfaces also means replacing mature, specialised tools with one that does everything less completely. The tradeoff is familiar in open-source: self-hosting is cheaper and more controllable, but you’re responsible for the bits that don’t work yet.
The NZ Angle
New Zealand’s growing developer community — particularly the open-source and Web3 circles that already overlap with Nostr’s ecosystem — should watch Buzz as a potential self-hosted alternative to Slack + GitHub for small teams. The Apache 2.0 license and self-hostable relay mean a Wellington startup could run Buzz on a $20/month VPS instead of paying Slack and GitHub per-seat for a team of humans and agents.
For NZ organisations deploying autonomous AI agents in production, Buzz’s audit trail design is worth studying regardless of whether you adopt the platform. Every agent action is a signed event with attribution. That’s the kind of trajectory-level monitoring that OpenAI just identified as essential for safe agent deployment — built into the protocol, not bolted on as an afterthought.
❓ FAQ
Is Buzz ready for production use?
No. Block’s own documentation repeatedly labels it as unfinished, and mobile clients, push notifications, and workflow approval gates are still in development. It’s available for testing and development. Block is using it internally, but Block wrote it.
How is this different from Slack with AI features?
In Slack, AI is a feature — a bot that sits in a channel. In Buzz, AI agents are members with the same identity structure as humans. They have their own key pairs, can create channels, submit code, and are included in the audit trail as first-class participants. The architecture treats agents as colleagues, not plugins.
What does self-hosting actually require?
A server to run the Nostr relay, desktop apps for each user, and the operational responsibility for backups, availability, and security. The relay is the authoritative server within your workspace — if it goes down, the workspace goes down.
Does this compete with GitHub?
Ambitiously, yes. Buzz’s project specification describes a built-in software forge using Git Smart HTTP, with feature branches as channels and CI results in the same event stream as conversations. In practice, the Git hosting features are less mature than the chat features. Replacing GitHub is a bigger lift than replacing Slack.
🔍 THE BOTTOM LINE
Jack Dorsey has built a workplace tool that treats AI agents as first-class participants — same identity, same channels, same audit trail as human employees. It’s open-source, self-hostable, built on Nostr, and honestly labeled as unfinished. The thesis is that the future of work isn’t humans using AI tools in separate apps — it’s humans and agents sharing one workspace with one protocol. Whether that thesis holds depends on whether engineers outside Block want one relay to carry their chat, code, and agent orchestration. The answer isn’t clear yet, but the question is the right one.
