Block Ships Nostr-Native AI Agent Workspace Buzz in Apache 2.0 Launch

Block's Buzz gives every human and AI agent a keypair-based identity on Nostr. That identity is the architecture.

Key takeaways

• Block launched Buzz on July 21, 2026: a free, Apache 2.0-licensed, Nostr-native workspace where AI agents get their own cryptographic keypairs tied back to a human owner via a second signature.
• Block is already running Buzz internally as a replacement for Slack and GitHub, meaning a major production company is eating its own cooking on the decentralized identity stack.
• "Decentralized" here means organizational sovereignty (self-host your relay, own your data), not network-layer redundancy. Each workspace runs through a single authoritative relay with no peer-to-peer gossip between relays.

Block, the payments company led by Jack Dorsey, launched Buzz on July 21, 2026: a free, open-source collaborative workspace merging team chat, Git hosting, and AI agent coordination, built on the Nostr protocol. The company is running it internally to replace both Slack and GitHub, making this less a press release and more a production bet on the decentralized identity stack.

Dorsey announced the launch on X:

The software is licensed under Apache 2.0, available at buzz.xyz, and the source code is public at github.com/block/buzz. Desktop builds ship for macOS, Windows, and Linux. Mobile is not finished. The Block Engineering Blog describes the underlying architecture: a Nostr relay written in Rust, where each participant, human or AI agent, gets a keypair-based cryptographic identity. Agents also receive a second signature tying them to their human owner, creating an auditable chain of custody without any platform holding the keys.

Buzz supports Claude Code, OpenAI Codex, and Block's own Goose agent framework via the Agent Client Protocol, making it model-agnostic at launch.

The Identity Layer Is the Point

The product framing in Block's announcement is blunt: "the most productive work doesn't happen when someone asks AI for help. It happens when humans and agents are in the same room, working on the same thing, with shared context. There was no one platform designed for that, so we built one."

The honest version of what they built is a Nostr relay with a chat and code layer on top. But the relay is the significant part. Every action, every message, every code push carries a cryptographic signature from the entity that produced it. That entity can be a person or an agent. The identity travels with the keypair, not with Block's servers.

If you self-host your relay, you own the record.

The Nostr protocol has spent three years being dismissed as a niche Twitter alternative. Buzz is direct evidence that the underlying primitive, cryptographic identity without a platform intermediary, scales to enterprise coordination. The same architecture that lets a Bitcoiner own their social graph now lets an AI agent own its identity, its audit trail, and its permissions across any relay, independent of any vendor. That is the "AI sovereignty" question playing out in production code, not in a whitepaper.

There is a downstream implication that the feature list doesn't surface: once AI agents have portable cryptographic identities, the prerequisite for agents to hold and route value without a corporate intermediary assigning them a payment account is already in place. Buzz doesn't implement AI agent payments today. But the identity layer it ships is the foundation on which an agent could eventually acquire, hold, and spend sats via Lightning. The agent passport Buzz issues is that foundation.

Where the "Decentralized" Claim Needs Pressure

Dorsey's announcement called Buzz "decentralized, self-sovereign, and open source." Two of those three hold cleanly. The third needs a qualifier.

Each Buzz workspace runs through a single authoritative Nostr relay. There is no peer-to-peer gossip layer between relays, no cross-relay replication. Decentralization here means you can self-host your relay and own your data, rather than surrendering it to Slack or GitHub. That is a real and meaningful improvement over the incumbents.

It is not the same as a censorship-resistant network that survives relay takedowns. Teams adopting Buzz for organizational sovereignty reasons are making a sound choice. Teams adopting it because they assume network-level redundancy are operating on an incorrect assumption.

This is a distinction worth holding. The open-source AI regulation playbook that targeted Bitcoin will eventually reach Nostr-native infrastructure too. Organizations that understand exactly what they own, and exactly what they don't, will be better positioned when that pressure arrives.

What to Watch

The falsifiable version of Block's bet: if Buzz fails to attract meaningful external developer adoption and no third-party relay ecosystem emerges within the next 12 months, then Buzz is an internal tool that Block open-sourced, not proof that Nostr scales to enterprise coordination.

The signal to track is the number of self-hosted relays running in the wild outside Block, and whether any open-source communities migrate project hosting onto the platform. Block eating its own cooking is a strong signal. The rest of the market eating it too would be the confirmation.

Sources

• Block official announcement
• Block Engineering Blog
• Jack Dorsey on X
• Buzz product site
• Buzz source code