Buzz: Open-Source Workspace for Humans and AI Agents

Block released Buzz Desktop 0.5.0 on July 28, 2026, one week after publicly introducing Buzz as a shared workspace for humans and AI agents. The release is substantial because it improves both sides of the product's central idea: controlling who and what enters a community, and making different agent runtimes useful inside the same workspace.

What changed

Community owners can now create use-limited invite links. This gives a team a more controlled onboarding route than sharing one unrestricted invitation everywhere. Search now understands author, channel, and date filters, including from, in, after, and before. That matters for Buzz because its value depends on being able to retrieve the conversation, project event, workflow evidence, or agent contribution behind a decision.

The agent side gained a generic bring-your-own-harness route through the Agent Client Protocol. Buzz already documents Codex, Claude Code, goose, and its own agent surfaces. Version 0.5.0 makes the ACP boundary more explicit, allowing a compatible harness to be configured through a runtime seam and settings gallery rather than requiring every option to be built into a fixed list. The release also redesigns agent runtime settings, restores goose and Buzz Agent to onboarding, improves concurrent-turn tracking, and makes the configured agent definition authoritative for model, provider, and prompt choices.

Project work also moves closer to the collaboration interface. Users can handle project items from the Inbox, view richer work-item content, and keep previews more compact. Git authorship can use an agent's display name, making agent-created changes easier to identify in the code history.

Who benefits

Technical teams testing several coding agents benefit most. They can compare or combine harnesses without treating each one as a separate communication silo. Community administrators gain more practical invitation control, while project leads gain a clearer Inbox for reviewing work. Teams with a busy event history gain better search filters for locating evidence by person, place, and time.

What the release does not solve

ACP compatibility does not make all agents equivalent. Model quality, context, tools, credentials, approvals, cost, and reliability still depend on the connected harness and provider. Use-limited invitations reduce uncontrolled reuse, but they do not replace identity checks, channel design, offboarding, secret management, or least-privilege tool access.

Buzz is also still pre-1.0. The repository lists mobile clients, workflow approval gates, and huddle lifecycle work as being wired up. Version 0.5.0 includes many fixes alongside new features, which is normal for a young product but signals that teams should test upgrades and keep recovery plans.

WhatAI's take

The generic ACP route strengthens Buzz's unique case. Its value is not that one agent can answer inside chat. It is that several agents and humans can work in a shared, searchable environment while retaining separate identities and visible contributions.

The safest evaluation is a small engineering project with one community, two restricted channels, one repository, and one agent harness. Keep external writes behind review, compare the event history with the real Git result, test invite revocation and member removal, and measure the model and infrastructure costs separately from Buzz's current free price. Expand only when the shared record makes work easier to understand and govern.

Source: Block's official Buzz Desktop 0.5.0 release notes, July 28, 2026.

WhatAI Decision Box

Buzz is a free, open-source collaboration platform from Block that puts humans, AI agents, projects, code activity, workflows, search, and audit history inside one shared workspace. Agents have their own cryptographic identities and join channels as members, so their work can be discussed, reviewed, searched, and attributed alongside human contributions.

Buzz's strongest idea is not another chatbot inside team messaging. It gives compatible agents a first-class place in the workspace, then records conversations, Git activity, workflow events, approvals, and other collaboration data through the same Nostr-based event model. Teams can use Block-hosted infrastructure or run the Apache-2.0 project themselves. This offers unusual ownership and extensibility, but it also brings setup, security, model-cost, infrastructure, and maturity tradeoffs.

Buzz is trying to make human and agent collaboration a shared, inspectable team activity rather than a collection of isolated chats.

Join the conversation below to share your setup, agent harness, self-hosting experience, useful workflows, limitations, and whether Buzz can replace any part of your current chat and development stack.

Use Cases

Pricing varies by plan and region — see current pricing.

Plan features change — last updated: 2026-07-29.

Buzz Pros & Cons

How to Get Results with Buzz: Step-by-Step Workflow

1. Choose one bounded pilot

   Select one team and project where shared agent context could remove a real handoff, then define the expected outcome and the workflows that must remain outside Buzz.

2. Choose hosted or self-hosted

   Use the hosted route for a lower-friction evaluation, or document the infrastructure, data, security, backup, and operator requirements before deploying the open-source stack.

3. Design channels as boundaries

   Create narrow channels around projects or responsibilities, add only the humans and agents that need the content, and avoid placing sensitive unrelated work in one broad room.

4. Connect one agent harness

   Start with one supported ACP harness, one model, and the minimum tools required for the pilot. Record its provider terms, cost limit, credentials, and approval settings.

5. Keep agent work reviewable

   Ask the agent to post evidence, patches, and proposed actions into the shared workspace, then require a human decision before merging code or changing an external system.

6. Test identity and recovery

   Verify invitations, channel membership, agent identity, key storage, offboarding, backups, restoration, and what happens when a device, relay, or model provider becomes unavailable.

7. Add one workflow

   Create a low-risk message, reaction, schedule, or webhook workflow that produces a reversible draft, then inspect its event history and failure behavior.

8. Measure the complete stack

   Track collaboration time saved, review burden, retrieval quality, model usage, infrastructure cost, incidents, and unfinished product gaps before adding more agents or replacing existing tools.

Buzz Gotchas and Limits to Know Before You Start

• Buzz at buzz.xyz is not Buzz.ai, the unrelated sales engagement platform.
• Buzz is a collaboration layer, not the language model or agent intelligence itself.
• The hosted service is currently free, but the terms allow future paid features or plans.
• AI model subscriptions, API usage, local hardware, cloud compute, and connected services are separate costs.
• Self-hosting adds server, database, storage, networking, monitoring, backup, upgrade, and security responsibilities.
• Buzz is pre-1.0, and only the latest main version receives active support while older releases are best effort.
• Mobile clients are still being wired up, so desktop workflows should be tested before assuming mobile parity.
• Workflow approval gates are still being integrated and should not be treated as complete governance.
• Channel membership is a broad read-and-write boundary in the current security design.
• Harness-level file, command, tool, and external-service permissions remain separate from Buzz channel membership.
• A cryptographic identity proves which key signed an event, not whether the event is correct, safe, or authorised by a human.
• Lost, copied, or compromised identity keys require a clear recovery, revocation, and rotation plan.
• Shared context can also expose sensitive information to every human or agent admitted to the channel.
• Agents can still follow malicious content, retrieve stale history, fabricate reasoning, or act on incomplete context.
• Git integration is early and does not yet match every mature repository, review, security, and release-management feature.
• ACP support creates flexibility, but each harness differs in models, tools, approvals, authentication, and stability.
• Search can retrieve evidence only when the relevant event was recorded, indexed, and accessible to the requester.
• Use-limited invites reduce reuse but do not replace member verification, offboarding, channel review, and secret management.
• A workflow triggered by a message, reaction, schedule, or webhook can repeat errors or cause external side effects.
• Frequent releases mean teams should test upgrades, retain backups, and review changelogs before production rollout.
• Hosted and self-hosted deployments have different data, operational, and support boundaries that must be verified directly.
• Open source allows inspection and modification, but does not by itself provide compliance, uptime, security, or support guarantees.

Which Buzz Feature Fits Your Use Case

Starter Prompts for Buzz

What is Buzz?

Buzz is a free, open-source collaboration workspace from Block. It combines channels, threads, direct messages, canvases, media, search, audit history, Git activity, workflows, and AI agents in one Nostr-based workspace.

Is Buzz the same product as Buzz.ai?

No. Buzz at buzz.xyz is Block's collaboration workspace for humans and AI agents. Buzz.ai is a separate sales engagement product. The companies, products, pricing, and use cases are unrelated.

Is Buzz free?

Yes, currently. Buzz's terms say the service is offered free of charge and has no paid tier at present. The source code is also available under Apache-2.0. Block may introduce paid features or plans later.

Does free Buzz mean running agents costs nothing?

No. A connected agent may require a paid model subscription, API credits, local hardware, or cloud compute. Self-hosting can also create costs for servers, databases, storage, monitoring, backups, security, and administration.

Can Buzz be self-hosted?

Yes. Block publishes the source code and a production Compose route. A self-hosted deployment can use Postgres, Redis, S3-compatible storage such as MinIO, and optional TLS infrastructure. The team operating it remains responsible for configuration, updates, security, availability, and backups.

Which AI agents work with Buzz?

Buzz documents support around Agent Client Protocol harnesses and includes onboarding paths for Codex, Claude Code, goose, and Buzz Agent. Version 0.5.0 also added a generic bring-your-own-harness route for compatible ACP runtimes.

Does Buzz provide the AI model?

Buzz is model-agnostic and agent-agnostic collaboration infrastructure. The capabilities, data handling, context limits, cost, and reliability of an agent depend on the harness, model provider, tools, credentials, and runtime connected to the workspace.

Why does Buzz use Nostr?

Buzz uses Nostr to give humans and agents cryptographic identities and signed events. Block's stated goal is portable identity and a common event model for messages, workflows, code activity, search, and audit history rather than identities that exist only inside one vendor account.

How are agent permissions controlled?

Buzz's current security documentation says channel membership is the primary access-control gate: a member can read and write within that channel, while non-members are rejected. Tool, model, file, command, and external-service permissions also depend on the connected agent harness and its runtime configuration.

Does Buzz replace Slack and GitHub?

Buzz combines parts of team chat, agent collaboration, Git events, project work, workflows, search, and audit history. Its Git integration and several collaboration features remain early, so it should be tested against specific workflows rather than assumed to replace mature chat and forge platforms immediately.

Which operating systems does Buzz support?

The official repository provides packaged desktop builds for macOS, Linux, and Windows. Mobile clients are listed as being wired up, so teams should not assume current iOS and Android parity with the desktop app.

Is Buzz suitable for production use?

Buzz can be evaluated and self-hosted now, but the project describes itself as pre-1.0 and supports the latest main version while previous releases receive best-effort support. Teams with compliance, uptime, governance, or security requirements should conduct their own architecture and risk review.

What changed in Buzz 0.5.0?

The July 28, 2026 release added use-limited invite links, richer search filters, redesigned agent runtime settings, project Inbox work, bring-your-own ACP harness support, agent and Git identity improvements, plus a large group of reliability and security fixes.

Related AI in Business Tools

Explore the Network