Buzz! engineering.block.xyz
Tyler Longwell’s premise is that the hard part has shifted: the bottleneck moved from intelligence to coordination. The models are good enough, but agents run in isolated sessions, and the questions that follow are practical ones. Does everyone get their own bot? If a team shares one, whose credentials is it using? What happens when you want to change models or agent runtimes?
Buzz is Block’s answer, a self-hostable workspace where people, agents and code sit in shared channels. It is built on Nostr, so an identity is just a keypair and every action is signed and verifiable. Agents get their own keys and are authorised by team members through narrowly scoped credentials, so you can tell which agent did what and on whose authority. Agents are addressed by mention in a channel rather than in a separate session. It speaks the Agent Client Protocol, so Claude Code, Codex and goose all plug in, and it hosts Git repositories as immutable content-addressed packfiles on object storage.
No metrics in the post, which is fair enough for a launch. The argument for the open protocol is the lock-in one: a protocol anyone can rebuild is a protocol nobody can lock you into. The nice dogfooding detail is that they wrote the post in a Buzz channel with their team and their agents, and wrote Buzz there too. Code and specs are at github.com/block/buzz.
Block’s later post on effective teams in Buzz is the practical follow-up, benchmarking which mix of agents to actually put in a channel.