Block Buzz Gives AI Agents a Cryptographic Identity

Daniel Reyes Principal Engineer (AI/ML), YuSMP Group · AI agents and applied LLM systems for US and EU teams

The short answer

What did Block actually ship?

Block, Jack Dorsey's payments-and-fintech company, released Buzz as a free, open-source workspace under the Apache-2.0 licence, available self-hosted from github.com/block/buzz or as a hosted version at buzz.xyz. On the surface it looks familiar — channels, threads, direct messages, voice, media sharing, code repositories and automated workflows in one place — and Block is explicit that it is going after companies whose work today is split across Slack and GitHub. The difference is who counts as a member: alongside people, AI agents join with their own accounts and permissions and can post, review code and kick off automations like a colleague.

The substance sits underneath, in identity. Buzz is built on Nostr, the decentralised messaging protocol, which gives every agent a cryptographic keypair that is independent of the platform itself. A second signature ties each agent to its human owner, producing what Block calls “a cryptographic paper trail that neither the human nor the agent could produce alone.” Patches, continuous-integration results and review comments are preserved alongside the discussion in a single audit record — so an agent's action is not an anonymous event in a log, but a signed, attributable one. This is the identity and provenance layer that most teams wiring up Claude Code and similar agents have been improvising by hand.

It is also deliberately open at the model layer. Buzz is model-agnostic and agent-agnostic, integrating agents through the Agent Client Protocol — an open standard — and supports Anthropic's Claude Code, OpenAI's Codex and Block's own goose framework out of the gate. Bradley Axen, Block's head of AI capabilities, framed the stakes plainly: “Every company is going to need a place where humans and agents work together. The question is whether that place is proprietary or open.”

Why does agent identity matter now?

Because teams stopped running one agent and started running many, and the tooling underneath was built for people. In Slack and GitHub, an AI agent typically shows up as an app, a bot, or worse, a shared service account — a single credential that several automations quietly reuse. That works until something goes wrong. When an agent pushes a bad change, contacts the wrong system, or approves a risky merge, “which agent, acting for whom” is exactly the question you cannot answer cleanly from a shared token.

Giving each agent its own cryptographic identity flips that. Block's own coding agent, BuilderBot, reportedly handles on the order of 200,000 operations a day and accounts for a meaningful share of the company's production code changes (as reported by The New Stack) — the kind of volume where anonymous automation becomes an operational and compliance liability. Identity plus a signed record means every agent action is attributable after the fact: who ran it, under whose authority, and what it touched. That is the difference between “the AI did it” and an event you can actually review.

The open, protocol-based design matters for the same reason. By putting identity in a Nostr keypair rather than in the platform, Buzz keeps an agent's identity from being locked to one vendor's walled garden — echoing the wider industry push toward open agent standards. Whether or not Buzz itself wins, the direction of travel is clear: autonomous actors need portable, verifiable identities, not borrowed human ones.

What are teams underestimating?

The first thing is maturity. Buzz launched at version 0.4.22, with Git integration described as early stage. A promising identity model does not make a young platform ready to carry your primary chat and code hosting tomorrow. The prudent read is to treat Buzz as an early reference implementation of an idea worth adopting, and to pilot it on internal, low-blast-radius work before betting workflows on it.

The second is that identity is not authorisation. Knowing which agent did something is necessary but not sufficient; you still have to decide what each agent is permitted to do. A cryptographic paper trail tells you an agent merged to main or emailed a system — it does not stop it. Scoped permissions, review gates on anything that ships, and a named human owner per agent are the controls that turn provenance into safety. Buzz gives agents individual accounts and permissions; using them well is still a design decision, not a default.

The third is governance and data control. Self-hosting gives you full control of the data; the Block-hosted option is convenient but puts your agents' activity on someone else's infrastructure — a real consideration for regulated FinTech and healthcare teams under GDPR and the EU AI Act. For those teams the upside is genuine: a signed record of who or what changed a system is precisely the evidence auditors ask for. But it only helps if the deployment, retention and access model are decided deliberately, not inherited from a default.

What it means for US & EU teams

The productive way to read this launch is not “switch to Buzz.” It is: agent identity and provenance are becoming table stakes, and now is the time to put them into your own agent workflows regardless of which tool you standardise on. If you already run coding agents through Claude Code, Codex or goose, the practical takeaway is to stop letting them act through shared credentials and start giving each one a distinct, attributable identity with a named owner and a durable record of what it did.

For regulated teams, the compliance angle is the sharp end. Under the EU AI Act and GDPR, an autonomous system acting on data or making changes is something you must be able to account for — who authorised it, what it did, whether the record was kept. A signed, per-agent audit trail is the difference between demonstrating control and hoping your logs are enough. That is a governance requirement you want designed in before you scale agents, not reconstructed after an incident.

There is a strategic point for engineering leaders too. If the workspace becomes the control plane for agents, the value compounds for teams that already treat access, identity and provenance as engineering assets: your humans and your agents run on the same clear permission model. Teams with ad-hoc bot tokens and murky ownership will instead get autonomous actions no one can fully attribute — at machine speed. Openness helps here: an open protocol and an open standard mean you are adopting a pattern, not a lock-in.

How to act on it this quarter

You do not need to migrate to Buzz to benefit from what it signals. Here is the shippable version.

1. Give every agent its own identity. Stop running coding or workflow agents through shared service accounts; issue each a distinct credential you can attribute.
2. Name a human owner per agent. Assign someone accountable for what each agent is allowed to do and for any impact it causes.
3. Keep a signed, durable record. Preserve which agent made which change, alongside the patch, CI result and review — not just an ephemeral chat log.
4. Separate identity from authorisation. Scope each agent's permissions tightly and gate anything customer- or production-facing behind human review.
5. Pilot Buzz on internal work. If the model appeals, trial it self-hosted on low-risk tasks before trusting it with primary chat or code hosting.
6. Decide data control up front. For regulated workloads, choose self-hosted versus hosted deliberately, with retention and access defined for auditors.

Used well, an agent workspace with real identity is a sensible consolidation: attributable actions, clear ownership, one governed place to watch a fleet of agents. Used carelessly, more autonomy on borrowed credentials just means faster mistakes no one can trace. The difference is the identity and provenance model you insist on — whichever tool you run it in.

Frequently asked questions

Sources

Block — Introducing Buzz: where humans and agents work together (primary source), 21 July 2026
SiliconANGLE — Block launches Buzz, an open-source workspace for humans and AI agents, 21 July 2026
The New Stack — Block built a Slack for AI agents, and gave each one its own passport, 21 July 2026