A Named Product, Not a Concept
On July 21, Block launched Buzz — a free, open-source workspace that combines team chat, AI agents, code repositories, and automated workflows in one interface. It runs on macOS, Windows, and Linux under Apache 2.0. It's self-hostable. It costs nothing to start.
The target is explicit: Slack (which Salesforce acquired for $27.7B) and GitHub. This isn't a startup fumbling toward product-market fit — it's a deliberate architectural counter-argument from someone who has built at scale.
The Architectural Bet Worth Watching
The design decision that matters most for operators isn't the price. It's that Buzz treats AI agents as first-class participants with cryptographic identities and scoped permissions — built into the permission model from day one, not added as an integration layer.
Contrast that with how most teams run agents today: bots wired into Slack via API, permissions managed outside the core system, audit trails that don't survive a configuration change. It works until it doesn't.
Buzz's model assumes your team already has — or will soon have — persistent agents doing real work alongside humans. If that's directionally true for your organization, the question stops being "which chat tool" and becomes "which collaboration environment was designed for this reality."
For non-tech companies especially, the gap between bolt-on AI and native AI is where implementations quietly fail. Agents that don't have coherent identity and permissions create shadow workflows, inconsistent outputs, and compliance exposure that nobody notices until a deal or audit surfaces it.
What Operators Should Do With This Now
Buzz is too new to recommend as a production environment for most teams. But its launch is a useful forcing function for two decisions:
First, audit your current agent permissions model. If your AI agents are operating through personal OAuth tokens or shared credentials, you have a risk surface that has nothing to do with Buzz — fix that regardless.
Second, treat this as competitive context for your Salesforce/Slack renewal conversations. Salesforce's Slack monetization story just got materially harder to defend at price. If you're mid-contract or heading into a renewal, the existence of a credible, free, agentic-native alternative changes your negotiating position even if you never deploy Buzz.
The product may or may not win. The architecture it represents is already the direction the market is moving. Operators who understand the difference between bolt-on and native AI in their collaboration stack will make better tooling and vendor decisions over the next 18 months.