Block's Buzz: Decentralized Workspaces for AI Agents
Indie Hacker Newsgo watch the original →
the gist
Buzz is an open-source, Nostr-based workspace where AI agents hold their own cryptographic identities, allowing them to sign commits and perform tasks alongside humans without platform-locked credentials.
Decentralized Agent Identity and Delegation
Buzz shifts the management of AI agents from platform-controlled settings to a decentralized protocol based on Nostr. Every agent is assigned its own cryptographic keypair, which allows it to sign commits and perform actions independently. This architecture solves the problem of credential management in teams where agents outnumber humans. The delegation model ensures that authorization does not overwrite authorship: the agent remains the author of its actions, while its credential provides a verifiable link to the human owner. If an agent key is compromised, the owner can revoke the specific agent credential without affecting the underlying human identity or other active sessions.
Protocol-Driven Collaboration
Buzz is model and agent agnostic, utilizing the Agent Client Protocol (ACP) to allow various runtimes like Claude Code, Codex, or Block's own 'goose' to operate within the same workspace. By integrating code repositories directly into the chat interface, the platform creates a unified, searchable record that includes discussions, patches, CI results, and signed merge decisions. This design aims to preserve the context of why specific code changes were made, rather than just storing the final diff. The system also supports distributed inference, allowing teams to route model requests to other members' hardware to share GPU and compute capacity.
Formalized Storage and Reliability
To ensure data integrity, Buzz treats Git repositories as immutable, content-addressed pack files managed by a mutable manifest pointer. Updates to this pointer occur via a conditional compare and swap operation, which is the commit point for the system. Block specified this Git storage protocol in TLA+ and model-checked it for durability, reconstruction, and concurrent push safety. Any storage backend must pass a conformance suite to be trusted by the system, ensuring that even if the hosted service disappears, the signed history and identities remain verifiable and portable.