Buzz
Your people, your agents, your project โ all in one place
204 followers
Your people, your agents, your project โ all in one place
204 followers
a new groupchat platform for teams of people and agents of all sizes, built to reduce our dependency on slack and github. model-agnostic, decentralized, self-sovereign, and open source. ๐
Free
Launch Team
AWS Activate CreditsCredits that fuel your startupโs next milestone
Promoted
Summarizing @jack's post on why Block is building Buzz:
Buzz: an open-source workspace for people and agents
Jack says Block released Buzz as an open-source workspace that puts people, agents, conversations, and code on equal footing behind one cryptographic identity system. He presents it as a way to reduce reliance on Slack and GitHub, solve the context-loss problem across tools, and create a signed, attributable record for work.
Key Takeaways
Buzz stores messages, patches, reviews, workflow steps, and approvals as signed events on a self-hosted relay.
It is built on @nostr, uses Apache 2.0, is model-agnostic, and already supports @codename goose, Codex, and @Claude Code.
The project is early but working on channels, threads, DMs, canvases, media, search, audit logs, workflows, and a desktop app, with Git hosting, mobile, push, and approval gates still coming.
Also, not sure who set this up, but can I join? ๐ฅบ
Possibly the most significant drop since Openclaw.
Coming from analytics and BI, the shared event log is the part that clicked for me. If messages, patches, workflow steps, and approvals all live in the same attributable history, Buzz could do more than reduce context switching โ it could make humanโagent work measurable.
Are you planning a higher-level analytics layer that turns those events into measures like handoff time, approval bottlenecks, workflow retries, or how often a human has to step in? That would help teams see where agents are actually improving the work, rather than just moving it around.
Congrats on the launch!
putting people and agents behind one identity system is the interesting bet here. question on the crypto identity side - if someone's key gets compromised, or an employee leaves, can you revoke or rotate their identity without breaking the signed history that already references it? self-hosted relay plus a permanent audit trail seems like it could get awkward if key rotation isn't a first-class thing
Teams of people AND agents in one chat is the right target โ most tools bolt agents on as webhook bots with a user account, and it shows. Question on identity: are agents first-class members with their own auth and permissions (what they can read, which channels they can post to), or do they inherit from whoever installed them? Once several agents work one project, per-agent scoping is what keeps the room trustworthy. Open source + model-agnostic is the right call for this layer.
signed events on a relay you self-host is a much more credible answer to the Slack/GitHub context-loss problem than yet another SaaS dashboard. the one thing I'd want cleared up before betting a team's workflow on it - if you lose the key tied to your cryptographic identity, is there any recovery path, or is that identity just gone and you start over? for a work tool that's a real question, not just a crypto-wallet edge case.