buzz

with a great tool that ships code, does research, and helps teams in the environment they actually collaborate in https://block.xyz/inside/block-rolls-out-builderbot-a-new-su... But... Slack was not built as a place to bring your own agent, and there are serious challenges around sharing an agent in a chat environment. Should everyone have their own bot(s)? Do we need thousands of Slack apps for that to work? If not, whose auth does it use? How does parallelism work across the workspace/channel/threads? What if I want a different LLM? Harness? Something special and unique for me or my team? These are not issues exclusive to Slack, of course, and I actually really like Slack. It’s just that the setup there doesn’t easily work for large flocks of agents. Obviously the Builderbot team and I got through this and made something that works well for us. But the experience made me want to do this kind of thing right from the beginning. So, Buzz. Any agent that supports ACP (https://agentclientprotocol.com/) can live in Buzz. We ship a minimal Buzz agent that I use for everything, but our team uses goose, Claude Code, Codex, and other agents. Your subscription should work in Buzz. And any LLM that can reliably make tool calls will work fine. We've even got a fun (very rough/early) mesh-llm inference setup built-in that enables you and your team to power your own agents using open models. Agents don't impersonate you, they're authorized by you. Cryptographically provable offline. Agents can start channels, archive them, add users and other agents to them. Whatever you can do in Buzz, they can do too. There’s a Buzz mobile app that lets you chat with your team and control your agents from anywhere. Your agents can run wherever as long as they can reach your team’s Buzz. Your laptop, your home server, any cloud. Your Buzz relay, has an S3 backed git server that agents automatically get their auth and signing set up for them on. We put together a rough proof for it because I couldn't find anyone else doing git in a provably safe way that scales like S3 does https://github.com/block/buzz/blob/main/docs/git-on-object-s... We've adopted standard Nostr message kinds and ideas and have put together a few more for agent specific functionality that we hope others mind find helpful https://github.com/block/buzz/tree/main/docs/nips There's a lot of fun stuff in Buzz to use and try out right now. We’ve got a sprawling vision for an open source, self-sovereign, vertically integrated, multi-player agentic workspace. It's still early days and still very, very rough, but I think this is a good way to do dev together with teams and agents going forward. Happy to answer questions and chat here. https://github.com/block/buzz