Team chat is becoming one of the next battlegrounds for AI agents. Buzz, a new open-source group chat app connected to Jack Dorsey’s Block, is built around a simple idea: people and AI agents should be able to work in the same channels instead of jumping between chat, code, tickets, and separate AI tools.
That puts Buzz in direct conversation with tools such as Slack, GitHub, and newer AI-native workspaces. The app is still early, but it points to a larger shift in workplace software. AI agents are no longer being treated only as side panels or prompt boxes. They are being designed as active participants inside the same spaces where teams already discuss work.
What Buzz Is
Buzz is a desktop app for macOS, Windows, and Linux that combines group chat with AI-agent workflows. Dorsey described it as “model-agnostic, decentralized, self-sovereign, and open source”, which is the kind of wording that needs the quotes because it is doing a lot of positioning at once.
In practical terms, Buzz looks like a team messaging app, but with AI agents built into the workspace. A team can use channels, discuss tasks, and bring agents into the same conversation. The pitch is that AI work should not be trapped in a separate chat tab when the rest of the team is making decisions somewhere else.
The official Buzz support page describes it as an open-source desktop app where users and AI agents work together in communities and channels. It also explains that Buzz uses relays to store and serve community content such as channels, messages, users, agents, and rules.
Why AI Agents Need A Different Workspace
Basic chatbots work fine as one-to-one tools. A user asks a question, gets an answer, and moves on. AI agents create a different problem because they can be assigned tasks, review context, generate code, propose changes, and run alongside other work.
That makes coordination harder. If one teammate is discussing product decisions in Slack, another is reviewing GitHub issues, and an AI agent is operating in a separate coding tool, the context gets scattered. Buzz is trying to reduce that fragmentation by putting more of the workflow in one place.
Tech Block Central recently covered how OpenAI’s ‘Codex Micro’ keypad makes AI agents feel more like desk tools. Buzz shows the same shift from another angle: AI agents are becoming something teams need to manage, monitor, and collaborate with in everyday workspaces.
Open Source Is A Key Part Of The Pitch
The open-source angle matters because workplace chat can hold sensitive information. If a product team is asking AI agents to review code, summarize plans, or handle internal discussions, companies will want more control over where data lives and how the system is configured.
Buzz allows developers to inspect and customize the code, which could make it more appealing to technical teams that do not want a closed, one-size-fits-all workflow. It may also help teams build features around their own internal processes instead of waiting for a vendor roadmap.
That does not remove every risk. Open-source software still needs maintenance, security review, governance, and careful deployment. But it does give technical teams more room to adapt the product if AI agents become a serious part of their daily workflow.
The Slack Comparison Is Obvious, But Not Complete
Buzz will naturally be compared with Slack because both products are built around workplace channels. The difference is that Slack was designed first for human communication, then expanded with integrations and AI features. Buzz is being framed from the start as a place where humans and agents work together.
That distinction could matter for startups that are already building with AI agents. A new company without years of Slack history may be more willing to test a different workspace if it handles agents, code, and team chat in a more native way.
Established companies will be slower to move. Switching workplace chat is painful. Message history, permissions, integrations, compliance needs, and team habits all make migration difficult. For those users, Buzz may be more interesting as a signal of where collaboration tools are heading than as an immediate Slack replacement.
Why Buzz Is Still Early
The main caution is that Buzz is still in its early stages. That matters because workplace communication tools need reliability more than novelty. If a team is going to trust a product with daily conversations and AI-agent coordination, it needs stable permissions, strong search, predictable notifications, security controls, and a clear admin model.
AI-agent behavior also needs guardrails. A shared channel is useful only if people understand what an agent can see, what it can do, and when it is acting on behalf of a user. Without that clarity, agent work can become messy fast.
That is the real test for Buzz and similar tools. The winning product will not simply add AI agents into a chat room. It will make agent work visible, auditable, and easy to control.
What It Means For Workplace AI
Buzz is worth watching because it treats AI agents as collaborators inside the workflow, not just assistants outside it. That may become the default direction for workplace software as agents move from experiments to actual team tasks.
The bigger question is whether teams want a brand-new workspace for agentic work or whether existing platforms will absorb the same ideas. Slack, GitHub, Microsoft Teams, and AI coding tools all have reasons to move in this direction.
For now, Buzz is an early but clear sign of the next phase: team chat is becoming less about messaging alone and more about coordinating humans, software, and AI agents in the same place. Would your team want AI agents inside its chat channels, or would that make the workspace harder to manage?
Further reading: Buzz support documentation.