Buzz turns Dorsey's agent-centered operating thesis into an open-source product. Its key bet is that shared identity and signed events can make agents accountable participants in software work.
Jack Dorsey (@jack) said in an announcement on X on July 21st that Block is launching Buzz, an open-source workspace designed to put employees, AI agents, conversations and software repositories behind one identity system.
Dorsey, Block's cofounder and Block Head, is pitching Buzz as a way to reduce Block's dependence on Slack and GitHub. The move takes his preference for open protocols into the daily machinery of software development, where teams typically spread discussions, source code, automated workflows and agent activity across several vendors.
Buzz also 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 rather than serve only as a productivity add-on. Buzz supplies an infrastructure layer for that thesis: Block's public repository documents a separate internal build configured for Block's relay and agent provider.
One workspace 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 agents receive the same basic identity structure, including their own key pairs, channel memberships and audit trails.
That design lets agents participate as members rather than conventional chat bots. 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.
Buzz's Git ambitions go well beyond posting repository notifications into chat. The project specification describes a built-in software forge using standard Git Smart HTTP. A feature branch can become its own channel, with patches, continuous-integration results, review comments and the merge decision preserved in the same record. Repositories, discussions and workflow history then share one search index.
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. The repository is licensed under Apache 2.0.
Decentralized control, centralized relays
... continue reading