Buzz [What It Changes]
TL;DR
Buzz is Block’s free, open-source workspace where humans and AI agents share the same channels, git projects, and automated workflows, each with a cryptographic identity.
As of July 21, 2026 it shipped as a desktop app for macOS, Windows, and Linux; mobile clients were unfinished, and the launch build was version 0.4.21 under Apache 2.0.
It runs on the Nostr protocol. Every message, review, and git event is a signed, hash-chained event. Each workspace still uses a single relay as its source of truth.
A 2-truck HVAC shop, a 10-person agency, or a solo clinic should care because the “who told the bot to do that?” problem is already on their floor — and Slack plus GitHub plus a side-chat with an agent is how that problem currently hides.
Key Takeaways
Buzz treats an agent like a coworker you add to a channel, not like a plugin you mention with an @.
Open source and Apache 2.0 mean you can self-host; Block also offers hosted infrastructure. Early-stage is the vendor’s own warning.
The honest limit is operational, not ideological: one relay per workspace, unfinished mobile, and a product Block admits is still finding its operating model.
Copy the audit pattern even if you never install Buzz: one thread that holds the diagnosis, the task, the fix, and the signed record of who approved it.
What Buzz is, in one sentence
Buzz is a group-chat and collaboration workspace, built by Block, in which every human and every AI agent holds its own cryptographic identity and the same kind of channel permissions.
A 10-person marketing agency already lives in Slack for clients, GitHub or a Google Drive for files, and a separate chat with Claude or Codex when someone needs a first draft. The HVAC dispatcher who texts a tech and then pastes the same note into a spreadsheet is running the same split. The clinic that takes a voicemail, types it into the practice system, and later asks an agent to summarize the day is running it too. Buzz’s pitch is that those three rooms become one, and the agent is a named participant instead of a paste buffer.
If you already route forms into a CRM, you have felt the cost of a handoff that is not in the same thread as the work. US Tech Automations is useful here as the place you keep the deterministic publish step while the chat layer experiments.
What shipped on July 21, 2026
According to TechCrunch, Jack Dorsey announced Buzz on Tuesday, July 21, 2026, as a Slack and GitHub challenger, with a free desktop app for macOS, Windows, and Linux and source on GitHub. TechCrunch notes Buzz’s own site says it was built by Block (Square, Cash App, Afterpay, Tidal) and quotes Dorsey calling it “model-agnostic, decentralized, self-sovereign, and open source.”
Decrypt, dated July 22, 2026, fills in the protocol and the version. According to Decrypt, Buzz launched at version 0.4.21, under an Apache 2.0 license at github.com/block/buzz, with mobile clients still unfinished, and with each workspace running on a single relay that the repository calls its “single source of truth.”
Block’s own launch post matches that framing. Bradley Axen, Head of AI Capabilities, is quoted: “Every company is going to need a place where humans and agents work together. The question is whether that place is proprietary or open.” The product page at buzz.xyz describes chat, specialized agents, and git projects in one workspace.
| Fact | Figure or date | Source page |
|---|---|---|
| Public launch | July 21, 2026 | TechCrunch |
| Launch version | 0.4.21 | Decrypt |
| Desktop later tagged | 0.5.20 (Aug 25, 2026) | GitHub block/buzz |
| License | Apache 2.0 (OSI submit Feb 8, 2004) | Apache / OSI |
| Repo commits (as fetched) | 2,579 | GitHub block/buzz |
| Repo branches (as fetched) | 971 | GitHub block/buzz |
| Nostr protocol repo stars | 12.0k | GitHub nostr-protocol/nostr |
| goose commits (as fetched) | 5,581 | GitHub aaif-goose/goose |
Sources: TechCrunch; Decrypt; GitHub block/buzz; 0.5.20 release PR; Apache 2.0; OSI Apache-2.0; Nostr; goose.
| Block context (Decrypt) | Figure |
|---|---|
| Jobs cut (Feb, Decrypt) | >4,000 |
| Share of staff (Decrypt) | ~40% |
| Implied pre-cut headcount if 4,000 = 40% (USTA) | 10,000 |
| BTC disclosed (Decrypt) | 28,355 |
| BTC marked value (Decrypt) | $2.2 billion |
| Launch version | 0.4.21 |
| Desktop tag ~5 weeks later | 0.5.20 |
Sources: Decrypt; GitHub block/buzz. The 10,000 row is USTA analysis.
How the mechanism works
You add an agent to a channel the way you add a coworker. The agent holds a keypair that belongs to it, not to a vendor account. It can post, review code, run approved automations, and keep a memory. Users set channel- or thread-specific rules. Decrypt reports that every message, reaction, workflow step, review approval, and git event is recorded as a single signed event in one log, with a hash-chain audit trail.
That log is Nostr’s idea applied to work. The Nostr protocol repository describes Notes and Other Stuff Transmitted by Relays: clients publish signed events to relays, followers fetch them, and relays can be hosted by anyone. Public-key cryptography is the tamper check. The companion NIPs repository documents optional “implementation possibilities”; NIP-01 is the basic flow. Nothing in that repo forces Buzz to implement every NIP. Buzz’s own repo, as Decrypt notes, still treats one relay as the workspace source of truth — decentralized identity, centralized log for that community.
Git sits inside the same window. According to the Git project homepage, Git is a free and open-source distributed version-control system whose latest source release is 2.55.0, dated June 29, 2026. Block’s launch post says the Git integration is early. The Nostr NIP-01 spec is the basic protocol flow Buzz is stacking work events on top of.
Agents are model-agnostic. Decrypt and Block both name Anthropic’s Claude Code, OpenAI’s Codex, and goose, Block’s own open-source agent framework. Claude Code’s product page lists a Pro plan at €15 per month with annual billing. goose’s GitHub page describes “an open source, extensible AI agent” and, as fetched, showed 5,581 commits.
Self-host or use Block hosting. The Apache License 2.0 grants a perpetual, worldwide, royalty-free copyright license and a patent license that terminates if you sue for patent infringement over the Work. The Open Source Initiative records the 2.0 text as submitted February 8, 2004. “Free” in Buzz’s marketing is the license and the desktop download, not a promise that self-hosting is zero ops.
Why now
Two constraints broke at once. Coding agents became good enough that a team’s “other coworker” is often a process, not a person. According to Slack’s pricing page, the free plan still caps message and file history at 90 days. Slack’s paid tiers add Workflow Builder, AI workflow generation on Business+ and Enterprise+, and HIPAA support only on Enterprise+. Buzz is Block arguing that the workspace for humans-plus-agents should be a protocol, not a seat. Agents that run code will still need a runtime: Node.js is the open-source JavaScript runtime those sandboxes typically ship, with the project’s own docs showing a local server on port 3000.
The company context is not subtle. Decrypt reports Block cut more than 4,000 jobs in February, roughly 40% of staff, with Dorsey writing in the Q4 2025 shareholder letter that AI “fundamentally changes what it means to build and run a company.” The same Decrypt piece says Block later disclosed 28,355 BTC worth $2.2 billion in a proof-of-reserves report. Those figures are about Block, not about Buzz’s user count — Buzz has not published one.
TechCrunch’s comparison set is already forming. Paradigm partner Georgios Konstantopoulos open-sourced Centaur, a self-hosted multiplayer agent runtime that talks in Slack or over an API. Centaur’s design is the opposite topology: the agent lives in Slack, each Slack thread gets an isolated sandbox, and a firewall injects secrets so the agent never holds raw keys. Buzz’s design puts the agent in the same native workspace as the humans and signs every event. Both are answers to “the lonely experience of working with AI agents,” a phrase Decrypt attributes to Block principal designer Thomas Petersen, who said the entire Buzz platform was developed using agents.
| Surface | Slack (public pricing page) | Buzz (launch materials) |
|---|---|---|
| Free message history | 90-day cap | Not stated as a cap; early product |
| Desktop OS | macOS / Windows / Linux (Slack clients) | macOS / Windows / Linux at launch |
| Mobile at launch | Yes | Unfinished |
| Agent identity | Apps / Slackbot on paid tiers | Cryptographic keypair per agent |
| License | Proprietary | Apache 2.0 |
| Default audit log | Paid / Enterprise features | Signed hash-chain events |
| Git in the same window | Integrations | Native (early) |
| HIPAA support | Enterprise+ only | Not claimed |
Sources: Slack pricing; TechCrunch; Decrypt; Block launch.
USTA analysis: 0.4.21 to 0.5.20, and 4,000 / 40%
USTA analysis. Two sourced pairs, no new measurements.
Pair one: Decrypt’s launch version is 0.4.21 (July 22, 2026 report of the July 21 launch). GitHub’s block/buzz tree, as fetched, includes a release commit “Buzz Desktop version 0.5.20” dated August 25, 2026, plus 2,579 commits and 971 branches. The public desktop moved at least one minor and one patch step in about five weeks (July 21 to August 25). That is a pace signal, not a stability signal. Early software that ships weekly is doing what 0.4.x software does; it is not a reason to port a 10-person agency off Slack this month. TechCrunch already said Buzz admits it is in its “early stages.”
Pair two: Decrypt’s job-cut line is “more than 4,000 jobs” and “roughly 40% of staff.” If 4,000 is 40%, implied pre-cut headcount is 4,000 / 0.40 = 10,000. Decrypt wrote “more than 4,000” and “roughly 40%,” so treat 10,000 as an identity check on those two figures, not as a headcount Block published. The point for a shop is narrower: the company that built Buzz just told shareholders that AI changes how a company is staffed. That is motive, not a recommendation to copy a 40% cut.
According to the BLS computer-support handbook, that reconstruction job still sits on 903,100 roles with median pay of $62,890 a year ($30.24 an hour) in 2025. A signed event log is how you stop paying that person to grep Slack. The BLS receptionist profile puts the person who actually answers the phone in a 10-person shop at a $38,010 median on 947,500 jobs.
What a small team should actually do
Do not migrate this week. TechCrunch said that out loud. Do steal four rules.
One thread holds the diagnosis, the task, the fix, and the conversation. Lucas Isaza’s argument, reported by Decrypt, is that Asana, Jira, and Linear baked sprints into the operating model; a configurable workspace makes the operating model the bottleneck. For a 10-person agency that already automates executive-assistant tasks, that means the client request, the draft, and the send approval live in one record.
Every agent has a name, a permission, and a kill switch. Buzz encodes that as a keypair and channel rules. You can encode it as a named workflow with a human publish step in US Tech Automations without touching Nostr.
The log is the product. If you cannot answer “which model, which prompt, which human said yes” six months later, you do not have an agent workspace. You have a paste buffer. The 2026 small-business automation landscape is the wider map; Buzz is one new room on it.
NIST’s AI Risk Management Framework (AI RMF 1.0, January 26, 2023, voluntary) is the overlay for anyone letting an agent touch a CRM or a repo. Buzz’s signed events help Map and Measure. They do not replace Govern. Self-hosting, Block says, means nothing routes through a third party unless you choose it. Hosted means you get protocol guarantees on managed infrastructure. Pick one in writing.
Agencies comparing Plutio alternatives or agency automation tools should treat Buzz as a collaboration layer, not as a replacement for dispatch, billing, or CRM. Dispatch software for agencies still owns the job board.
Honest limits
Buzz has not published seat counts, uptime, or a security audit in the pages opened for this hub. Mobile was unfinished at launch. Decrypt is explicit that despite the “decentralized” framing, each workspace runs on a single relay. Isaza said Block has “yet to figure out” the operating model that gets the most from Buzz. Petersen said the interface was “more sculpted over time than designed up front.” Those are primary-source cautions, not reviewer snark.
Nostr itself is a social protocol, not an enterprise compliance program. The protocol README is public domain; Buzz is Apache 2.0. Identity portability across Nostr-compatible systems is a design claim. Whether your accountant, your MSP, and your client will ever join that network is an adoption question the launch posts do not answer.
Centaur shows the other fork: stay inside Slack, isolate each thread in a sandbox, never let the agent see raw secrets. Buzz shows the native-workspace fork. Neither has published a small-business case study in the sources used here.
Signal vs Speculation
Signal (sourced). Launch July 21, 2026. Version 0.4.21 at launch; desktop 0.5.20 tagged August 25, 2026. Apache 2.0. Desktop for macOS, Windows, Linux. Mobile unfinished. Nostr plus one relay per workspace. Agents on Claude Code, Codex, goose. Block job cut: more than 4,000 roles, roughly 40%. Slack free history: 90 days. Git 2.55.0 dated June 29, 2026. Nostr repo 12.0k stars. goose 5,581 commits as fetched.
Our read (12–36 months, small and mid-size). If signed, portable agent identity becomes a procurement checkbox, Buzz-like workspaces will show up in agencies that already self-host. If not, Slack will absorb the agent as another paid feature (it already lists AI workflow generation on Business+ and Slackbot on Business+ / Enterprise+) and Buzz will remain a protocol experiment for teams that want to own the relay. The failure mode is operational: a 10-person shop that self-hosts a 0.5.x desktop and then discovers the person who understood the relay left. The useful steal is the audit trail, not the bee logo.
Our read on workflow. Teams that already keep a human on the publish step in US Tech Automations should not rebuild that step inside Buzz. Wire the chat record to the workflow, or skip Buzz and keep the signed approval in the system you already run. The agentic-workflow shape is the same either way: named agent, named permission, named human.
Glossary
Buzz. Block’s open-source workspace for humans and AI agents sharing chat, git, and workflows.
Nostr. Notes and Other Stuff Transmitted by Relays; signed events, many relays, no required central server.
Relay. A server that stores and forwards Nostr events. In Buzz, one relay is the workspace source of truth.
Keypair / nsec. The cryptographic identity of a human or an agent; the private key is the identity.
NIP. Nostr Implementation Possibility; an optional spec, not a mandatory checklist.
goose. Block’s open-source agent framework that Buzz can run alongside Claude Code and Codex.
Apache 2.0. OSI-approved license with copyright and patent grants, and a patent-termination clause if you sue.
Hash-chain audit. Each event points at prior events so tampering is visible.
FAQ
What is Buzz?
Buzz is a free, open-source group-chat and collaboration platform from Block in which humans and AI agents share channels, git projects, and workflows, each with a cryptographic identity.
Is it a drop-in Slack replacement today?
No. TechCrunch reports Buzz admits it is in early stages, and Decrypt reports mobile clients were unfinished at version 0.4.21.
Who built it?
Block, Jack Dorsey’s company. Dorsey announced it on July 21, 2026. The source is at github.com/block/buzz under Apache 2.0.
Does “decentralized” mean there is no server to run?
No. Identity is designed to be portable on Nostr. Decrypt reports each Buzz workspace still runs on a single relay as its source of truth. Self-hosting means you run that relay.
Which models can agents use?
Block and Decrypt both say the workspace is model-agnostic, naming Claude Code, Codex, and goose.
What should a 10-person agency do this month?
Keep Slack or email. Require every agent action that can send a client message or merge a PR to live in one thread with a named human approval. If you already enforce that in US Tech Automations, do not duplicate it inside a 0.5.x desktop. Revisit Buzz when mobile exists and a second production shop publishes a write-up.
A team that wants the signed-approval pattern without waiting on a 0.5 desktop can keep the human publish step on agentic workflows and treat Buzz as an optional chat layer later.
About the Author

Helping businesses leverage automation for operational efficiency.
Related Articles
See how AI agents fit your team
US Tech Automations builds and runs the AI agents that handle this work end to end, so your team doesn't have to.
View pricing & plans