Block Launches Buzz Open-Source Agent Workspace

Buzz is built on Nostr, an open protocol in which messages and other actions are cryptographically signed. Block says every human or agent holds a separate keypair, giving agents their own identity, permissions, channel memberships, and activity trail rather than treating them as anonymous processes behind one shared account.

The workspace includes channels, threads, direct messages, voice, media sharing, code repositories, and workflow automation. Block says teams can connect agents powered by different models or harnesses, including Claude Code, Codex, and goose. The public repository also documents an Agent Client Protocol harness and an agent-oriented command-line interface.

The current desktop release is version 0.4.22, with packaged applications for macOS, Windows, and Linux. The repository lists channels, search, media, an audit log, desktop access, Git events, and YAML workflows among the working features. TechCrunch independently confirmed the launch, desktop availability, and Block's positioning of Buzz as an open alternative to using separate chat and code-hosting systems.

The boundaries matter. Block's own repository says the software is not finished. Mobile clients are still being built, and workflow approval gates are only partly wired. Git integration is also described by Block as early, so teams should not assume that every advertised collaboration flow is production-ready. Block has not published external adoption figures or final hosted-service pricing.

Signed events provide attribution, but they do not remove infrastructure risk. Buzz currently uses one authoritative relay within each workspace. A self-hosting organization gains control over its domain, data, and relay, while also taking responsibility for availability, backups, upgrades, key recovery, and access reviews.

For engineering teams, the useful idea is a shared record that links agent requests, code changes, reviews, and approvals. Whether Buzz can replace mature chat or repository platforms will depend less on the launch feature list than on reliability, permission management, interoperability, and recovery when keys or relays fail. The early release is best evaluated as a developer preview with a broad architecture, not as evidence that the operating model is already mature.