AI Pulse · AI Trends Pulse

Block just open-sourced Buzz, a group chat platform built specifically for teams that work with AI agents. The pitch is simple: give every agent the same cryptographic identity, permissions, and audit trail you’d give a human teammate. It’s built on Nostr and released under Apache 2.0, so anyone can fork it or run their own instance.

Jack Dorsey’s team is positioning this as a direct replacement for Slack and GitHub when agents are doing real work alongside people. The idea is that you shouldn’t be copying and pasting API keys into a chat window or wondering which bot did what three weeks ago. Buzz treats agents as first-class participants with proper access controls and a full history of what they touched. The Hacker News thread pulled 365 points and 325 comments on launch day, which tells you the problem resonates.

What this means for your business

If you’re running agents in production, you’ve already hit the permission problem. Who can this agent talk to? What can it change? How do you revoke access without breaking three workflows? Most companies are duct-taping this together with Slack bots and spreadsheets. Buzz is betting that treating agents like employees, with real identities and audit logs, is the cleaner path.

You don’t need to rip out Slack tomorrow. But the conversation is shifting from “can we use AI?” to “how do we govern it when it’s running unsupervised?” Platforms like this, and the kind of orchestration layer we build into the Omni Command Centre, are responses to that shift. Open source means you can test it without vendor lock-in. Whether Buzz specifically wins doesn’t matter as much as the pattern it’s validating: agents need infrastructure, not just API access.