Jack Dorsey has unveiled a new workplace collaboration product called Buzz, positioning it as an alternative to Slack for teams that want to work alongside AI agents inside a single chat environment. According to TechCrunch, Buzz is designed to put people and software agents into the same conversations while also pulling in development workflows that normally live elsewhere.

The launch matters because it points to a more specific next phase in workplace AI: not just adding a bot into existing chat tools, but rebuilding the collaboration layer itself around agents, code, and self-hosted control. TechCrunch reported that Buzz was built by Block, the company behind Square, Cash App, Afterpay, and Tidal, suggesting this is more than an experimental side project from Dorsey.

A chat app aimed at Slack and GitHub at the same time

Based on TechCrunch’s reporting and Dorsey’s comments on X, Buzz is meant to reduce dependence on both Slack and GitHub by combining team chat, AI-native workflows, and project management into one interface. That is a notable framing. Many companies today use Slack for communication and GitHub for software collaboration, then layer separate AI tools on top. Buzz appears to start from the assumption that those boundaries are inefficient if AI agents are becoming active participants in work.

TechCrunch described the product as looking similar to Slack, but with native support for AI agents and the ability to manage GitHub projects from the same window. If that approach holds up in practice, it could appeal to engineering-led teams that want fewer context switches between messaging, coding, and agent-driven task execution.

Dorsey said Buzz is “model-agnostic, decentralized, self-sovereign, and open source.” Those labels matter for a certain slice of the market. Model-agnostic suggests teams are not locked to one model provider. Decentralized and self-sovereign suggest a product architecture that gives organizations more control over data and deployment. Open source, meanwhile, makes Buzz easier to inspect, modify, and potentially self-host.

That mix also fits Dorsey’s broader product philosophy. He has often backed open protocols and developer control rather than tightly managed closed platforms. In this case, that philosophy is being applied to enterprise collaboration, an area where incumbents such as Slack have typically emphasized managed SaaS convenience over deep infrastructure flexibility.

Why Block is backing this now

The timing reflects a broader shift in how startups and technical teams are experimenting with AI agents. As TechCrunch noted, teams increasingly rely on agents to complete work, but collaboration often remains fragmented across multiple products and windows. A messaging layer that treats agents as first-class participants is an attempt to solve that fragmentation.

Buzz also appears to fit with Block’s history of building developer-oriented and infrastructure-heavy products. While Block is best known for consumer and merchant services such as Square and Cash App, its backing gives Buzz more weight than a typical open source launch from an independent developer collective. Even so, there are still important unknowns. The available reporting does not describe whether Buzz is being rolled out internally at Block at scale, whether there is a commercial roadmap, or how tightly it will be integrated with other Block systems.

That uncertainty matters for enterprise buyers. A product can be technically interesting without yet being operationally ready. TechCrunch said Buzz itself acknowledges it is in its “early stages,” which suggests teams should view it as an emerging platform rather than a drop-in replacement for established workplace software.

Open source and self-hosting are central to the pitch

One of Buzz’s clearest differentiators is that the source code has been published on GitHub and the app is available as a free desktop product for macOS, Windows, and Linux. For developers and infrastructure teams, that lowers the barrier to testing and customization.

TechCrunch reported that organizations can tailor their own Buzz instance to match internal workflows because they have access to the code. That could be meaningful for companies that want custom agent behavior, proprietary integrations, or stricter control over where data is stored and processed. In sectors with security or compliance demands, self-hosting can be more than a preference; it can be a procurement requirement.

At the same time, open source does not automatically make a collaboration product enterprise-ready. Buyers still need to evaluate identity management, permissions, auditability, uptime expectations, governance over AI agents, and long-term maintenance. The evidence available so far speaks more to Buzz’s architectural direction than to its maturity on those operational fronts.

Competition is not just Slack, but the “AI inside Slack” model

Buzz enters a market where many companies are trying to retrofit AI into existing workplace tools rather than replace them. TechCrunch highlighted Centaur, an open source product recently introduced by Paradigm partner and CTO Georgios Konstantopoulos, as another effort in this category. Konstantopoulos described Centaur as a “virtual employee” that can operate inside Slack or through an API.

That contrast is useful. Centaur appears to assume Slack remains the center of work and that agents should live within it. Buzz makes a more ambitious bet: that if agents are important enough, teams may want a new interface designed around them from the start.

For Slack, the threat is not simply another chat app. It is the possibility that AI-native teams, especially new startups without entrenched habits, may choose a different system of record for communication and execution. TechCrunch explicitly noted that newer startups using AI agents and lacking an established Slack footprint may find Buzz or similar tools worth exploring.

Still, the burden of proof is high. Slack has years of organizational adoption, app integrations, admin tooling, and user familiarity. Replacing that is difficult even when a challenger offers a cleaner architecture. For many companies, especially larger enterprises, the more likely short-term path is to experiment with agents inside existing tools rather than migrate collaboration entirely.

Evidence, claims, and what is still unproven

The strongest confirmed facts in this story come from TechCrunch’s reporting and Dorsey’s public post: Buzz exists, Block built it, it is available now as a desktop app for macOS, Windows, and Linux, and its code has been uploaded to GitHub. The product is positioned against Slack and GitHub and is intended to support both people and AI agents in shared conversations.

Several of the most attractive attributes, however, are still claims or early descriptions rather than independently verified outcomes. “Model-agnostic,” “decentralized,” “self-sovereign,” and “open source” are part of Dorsey’s own characterization. TechCrunch’s account that Buzz can merge multiple workflows into one workspace provides helpful context, but there is not yet public evidence in the source material about large-scale usage, production deployments, security certifications, or measured productivity gains.

The same caution applies to the market thesis around AI agents. It is reasonable to say that startups are increasingly experimenting with agent-based work, as TechCrunch reported. It would be less certain to conclude from the current evidence that most enterprises are ready to adopt a new collaboration stack built around those agents.

What this means for builders and enterprise teams

For AI builders, Buzz is interesting because it treats the interface layer as part of the AI product, not just a wrapper. If agents are going to coordinate tasks, inspect code, trigger actions, and report progress, the chat workspace becomes an orchestration surface. A tool like Buzz could make it easier to prototype agent teamwork patterns that are awkward inside a conventional messaging app.

For product teams, the open source angle may be the most practical draw. Companies can adapt Buzz to specialized workflows instead of waiting for a vendor roadmap. That is appealing if a team wants a custom AI agent setup tightly connected to internal repos, tickets, or review loops on GitHub.

For enterprise AI buyers, the calculus is more mixed. The self-hosting and control message is attractive, especially in regulated environments. But the early-stage status raises immediate questions about support, administration, compliance, and migration cost. In many enterprises, replacing Slack is not a feature decision; it is a change-management project.

The bigger strategic signal is that workplace automation may move from add-on assistants toward shared environments where humans and AI agents operate as peers. Whether Buzz itself becomes important at scale or not, the product highlights where some builders think workplace software is heading.

What to watch next

The next useful signals are concrete, not rhetorical. First, watch whether Block discusses internal use of Buzz or publishes more technical documentation about deployment, integrations, and governance. Second, watch the GitHub repository for development velocity, external contributors, and signs that developers are extending the platform beyond the initial release.

Third, pay attention to whether Buzz remains focused on technical teams or broadens into a general workplace product. A tool that replaces both Slack and GitHub has a very different adoption path from one aimed mainly at developer organizations. Finally, watch how competing products such as Centaur evolve. The market may split between AI-native collaboration tools and agent layers embedded inside existing platforms like Slack.

Creati.ai perspective

Buzz is less important today as a direct Slack replacement than as a statement about where AI collaboration software may go next. Dorsey and Block are betting that agents should not be side-panel helpers bolted onto legacy workplace tools. They should live in the core workflow, share context with humans, and operate inside systems organizations can inspect and control.

That vision is plausible, but the hard part is not launching an open source desktop app. It is proving reliability, governance, and workflow value in real teams. If Buzz gains traction, it will likely start with builders who already care about self-hosting, GitHub-centric work, and customizable AI agents. The broader market will need evidence that the architecture is not just more open than Slack, but better for day-to-day execution.