Dorsey's Buzz Gives AI Agents Their Own Keys

Jack Dorsey's Block shipped Buzz today: an Apache-2.0, self-hostable workspace where team chat, AI agents, workflows, and Git live in one place, with every action — human or agent — recorded as a cryptographically signed Nostr event. The pitch is a Slack-plus-GitHub replacement for the agent era. That pitch will get the headlines, and it's the least interesting part of the launch.

The interesting part is buried in the architecture: Buzz gives every AI agent its own keypair.

The actual idea: agents with identities, not borrowed credentials

Today, when you wire Claude Code or a CI bot into Slack and GitHub, it acts with borrowed authority — a bot token, a PAT, often scoped wider than anyone remembers. When something lands in a repo or a channel, "who did this, and under whose authorization?" is a forensics exercise across three audit logs.

Buzz's answer is to make identity the primitive. Every participant holds a Schnorr keypair that belongs to them, not the platform. Agents sign their own work under their own identity; a human grants them narrowly scoped authorizations that don't transfer the human's identity. Block's engineering write-up puts it crisply: authorization does not erase authorship. Compromise an agent's key and you revoke that key — your own identity is untouched. The agent can run anywhere with a connection to the relay: your laptop, a VM, an edge box.

That's a genuinely better model than what Slack and GitHub offer, and it addresses a problem teams are hitting right now. A Slack engineer in the Hacker News thread described how hard it is to keep multi-user agents from leaking information across access boundaries — precisely because agents in today's platforms are grafted-on bots with pooled permissions rather than first-class actors with their own scoped credentials. Buzz is the first shipping product I've seen that takes the obvious-in-retrospect position: if agents are going to be coworkers, give them employee badges, not the master key.

What you actually get today

Under the hood it's a Rust workspace (Axum, Postgres with full-text search, Redis, S3/MinIO), with Flutter/Tauri clients for desktop and mobile. The server is a Nostr relay implementing NIP-01, NIP-42 auth, and NIP-34 git events; it's the source of truth for channels, search, and automation. Setup is Docker plus just setup && just build && just dev, or you can use Block's hosted instance at buzz.xyz.

Agent integration is where the developer story gets concrete. buzz-cli speaks JSON in and out, built deliberately for LLM tool calls. An ACP harness (buzz-acp) plugs in anything that speaks the Agent Client Protocol — Claude Code, Codex, Block's own Goose. Model-agnostic is real here, not marketing: swap the model or runtime and the agent keeps its identity, permissions, and history.

The Git story deserves both credit and a caveat. Block redesigned repository storage for agent-scale concurrency: immutable content-addressed packfiles plus a single mutable manifest pointer, with pushes landing via compare-and-swap and backends validated against a TLA+-derived conformance suite. That's serious engineering for a world where a dozen agents push simultaneously. But the README is more honest than the launch posts: git hosting as a forge replacement sits in the "strong opinions, pending code" column. What works today is git events — patches, announcements, status — flowing through the relay as signed Nostr events, plus git-sign-nostr for signed commits. Nobody is migrating off GitHub onto this in July 2026, and Block says as much: the project is explicitly "not finished," and they warn you off building compliance programs on features still being wired up.

Prior art, and why bundling cuts both ways

None of the individual pieces is new. Matrix and Zulip have done open, self-hostable team chat for a decade. Radicle has run sovereign Git on cryptographic identities for years, and NIP-34 git collaboration already had a small Nostr ecosystem. Goose covered the agent framework. What Buzz adds is the fusion — one signed event log spanning conversation, code review, workflow gates, and git pushes, so an agent's entire trail is queryable in one place.

That fusion is also the adoption problem. Teams don't switch chat platforms incrementally; Slack's gravity is enormous, and "also replace your forge" doubles the ask. The HN crowd's skepticism is fair on this point — several suggested Block should have partnered with an existing forge like Forgejo rather than building storage from scratch — and Dorsey's scattershot record (Bluesky spun out, Bitchat, Sup?, now this) doesn't inspire confidence in long-haul focus. The launch-day site reportedly pinning CPUs at 750% didn't help the execution narrative either.

There's competitive convergence worth noting too: Paradigm's Georgios Konstantopoulos released Centaur, an open-source "virtual employee," the same week. The "where do humans and agents work together" land grab is officially on, and Bradley Axen, Block's head of AI capabilities, framed the stakes accurately: the question is whether that place is proprietary or open.

The verdict

As a Slack killer, Buzz is a long shot — chat network effects have buried better-funded challengers, and the Nostr layer adds conceptual overhead most teams won't pay for a messaging app. As a GitHub killer, it isn't even shipping yet.

But as a reference architecture for agent-native collaboration, it matters. Per-agent cryptographic identity, revocable scoped authorization, and a unified signed audit log are the right answers to questions every platform team will be forced to answer within a year — GitHub and Slack included. If you're running multiple coding agents today, spin up a Buzz relay in Docker this week and study the authorization model, because you'll be implementing something like it regardless of whether Buzz survives. The product may lose. The identity model is going to win.