Block Buzz: Combining Team Chat, AI Agents, and Git Hosting
Block has launched Buzz, an open-source workspace designed to consolidate team chat, AI agents, and software repositories under a single identity system. By integrating these traditionally separate functions, Block aims to reduce its reliance on third-party vendors like Slack and GitHub while treating AI agents as first-class citizens within the organizational structure.
Unified Identity for Humans and AI Agents
Buzz treats AI agents as full members of the workspace rather than external bots. Both human employees and AI agents share the same basic identity structure, utilizing their own key pairs, channel memberships, and audit trails.
This architecture allows agents to perform complex tasks natively within the workspace, including:
- Searching prior discussions and opening repositories.
- Submitting patches and reviewing code.
- Running workflows and editing shared canvases.
- Creating new channels.
To maintain model flexibility, Buzz includes an agent-oriented command-line interface and supports harnesses for Goose, Codex, and Claude Code, decoupling the workspace infrastructure from the specific LLM being used.
Integrated Git Hosting and Software Forge
Buzz extends beyond simple repository notifications by implementing a built-in software forge using standard Git Smart HTTP. This integration allows the development lifecycle to be captured within the event stream:
- Branch-as-Channel: A feature branch can function as its own communication channel.
- Unified Records: Patches, continuous-integration (CI) results, review comments, and merge decisions are preserved in the same record as the discussion.
- Centralized Search: Repositories, discussions, and workflow histories share a single search index, reducing the context-switching typically required between a chat app and a Git host.
Architecture: Decentralized Ownership via Nostr
Buzz is built on a self-hostable Nostr relay, where every action—messages, reactions, workflow steps, and code events—is stored as a cryptographically signed event.
While the system is described as decentralized, the current architecture relies on a centralized relay model for each workspace. There is no peer-to-peer event exchange or replication between relays; all reads and writes pass through a single authoritative relay that handles authentication and distribution. The "decentralization" refers to deployment and ownership: organizations can run their own relays to retain control over their data and use portable Nostr key pairs, avoiding lock-in to a single hosted service provider.
Current Feature Set and Status
As of version 0.4.21 (released July 21, 2026), Buzz is available for testing and development but is explicitly labeled as unfinished.
Available Features:
- Channels, threads, and direct messages.
- Shared canvases and media support.
- Audit logs and search.
- Desktop applications for macOS, Windows, and Linux.
- YAML-based workflows.
Pending Development:
- Mobile clients and push notifications.
- Completed execution paths for workflow approval gates (currently lacking some database, API, and interface components).
Community Insights and Technical Critiques
Technical discussions surrounding the launch highlight several tensions regarding the "all-in-one" approach and the use of Nostr:
Data Privacy and Agent Access
Critics point out the inherent difficulty in managing permissions when agents have broad access to workspace data. One contributor noted:
"The challenge comes when you want to make certain things private to certain people. In that world you don’t want multiplayer agents leaking data, so you end up having to write and maintain complex rulesets about what specific resources agents have access to."
The Utility of Nostr in Enterprise
Some developers questioned whether the cryptographic signing and Nostr protocol add tangible value to a corporate environment compared to traditional self-hosted tools like Zulip.
"Is Nostr doing anything here that is actually a value add, vs a processing tax that could be done more efficiently with a shared service?"
Market Positioning
While some see Buzz as a necessary evolution to replace "walled gardens" like Slack, others argue that the moat is small and that major AI labs (like Anthropic or OpenAI) could easily integrate similar forge and chat capabilities into their own ecosystems, potentially steamrolling independent implementations.
Sources
Related
- Dispatch
- Dispatch
- Project
- Project
- Project