Buzz - Your people, your agents, your project β€” all in one place

byβ€’
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. 🐝

Add a comment

Replies

Best
Hunter
πŸ“Œ

Summarizing 's post on :

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 , uses Apache 2.0, is model-agnostic, and already supports , , and .

  • 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? πŸ₯Ί

wss://producthunt.communities.buzz.xyz
LOVE the design of your landing page! Huge congrats on the launch! πŸŽ‰ Buzz's approach of putting humans and AI agents into a shared workspace with native Git and Nostr identities is brilliant. Quick question: How are you managing permission isolation to ensure autonomous agents don't leak context across restricted channels?

Signed events for every message, patch and approval sounds great for audit. But in daily use, does the team notice the crypto identity layer at all, or is it fully invisible once you're in? Asking because most "self-sovereign" tools I've tried make you think about keys more often than you'd like.

Honestly, Buzz is awesome. Having my team and AI tools all working in the same spot saves us so much time. We don't have to jump between five different apps anymore just to chat, organize tasks, and get work done. Really loving it so far!

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!