Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

Jack Dorsey’s new project Buzz — an open-source, self-hosted workspace that combines team chat, AI agents, and Git hosting on top of the Nostr protocol — is prompting mixed reactions. Commenters see potential in “agent-first” collaboration and stronger data ownership but question whether Nostr and custom Git hosting add real value over existing tools like Slack, Zulip, or GitHub, and highlight thorny issues around permissions, privacy, and agent behavior in multi-user environments. Many are also skeptical about product quality, long-term support, and Dorsey’s track record, viewing Buzz as part of a broader AI hype cycle that may or may not translate into durable, trustworthy infrastructure for real-world teams.

Overall concept & positioning

  • Buzz is presented as an open‑source, self‑hosted workspace combining team chat, AI agents, and Git hosting, backed by Nostr-signed events.
  • Some see it as “bots in chat rooms plus Git” with heavy marketing; others think it’s an interesting “agent‑first” rethinking of dev collaboration and the future IDE.

AI agents in chat

  • Several commenters like the idea of “multiplayer” agents embedded in team workflows, seeing chat as a natural hub for human–agent collaboration and process automation.
  • Others are wary of “agent slop,” easy abandonment, and products that feel quickly LLM‑generated and disposable.
  • There’s concern that calling agents “teammates” is dehumanizing; some want agents treated as tools, not coworkers.
  • Some report strong productivity gains from LLMs and expect more tools like this; others argue this is a hype bubble or at least over‑marketed.

Permissions, privacy, and security

  • Big focus on access control: how to prevent multi‑user agents from leaking information across channels and groups.
  • Single‑user agents are seen as simpler; multi‑user agents require complex ACLs and careful scoping to avoid sharing confidential data.
  • Examples from Slack and other tools highlight real risks of data leakage, especially in leadership/HR channels and regulated environments.

Nostr, decentralization, and identity

  • Supporters like Nostr for portable, cryptographically signed identities and decentralized control over data and relays, avoiding vendor lock‑in.
  • Skeptics question whether Nostr adds real value versus a simpler self‑hosted chat (e.g., Zulip/Matrix) with conventional auth.
  • Some note the protocol choice may be driven partly by existing investments and ideology.

Git hosting and integration

  • Doubts that Buzz can match the polish and ecosystem of GitHub/GitLab; some suggest integrating with an existing forge instead of re‑implementing one.
  • Others see value in vertical integration: unified context across code, chat, and agents could enable richer workflows.

UX, performance, and adoption

  • Multiple people report the marketing site is extremely CPU‑heavy and laggy, reinforcing perceptions of “AI‑coded slop.”
  • Many say they wouldn’t churn from Slack/Teams just for “agent‑first” features; incumbents could add similar capabilities.
  • Nonetheless, some are eager for a credible, open, self‑hosted alternative to Slack/GitHub and plan to experiment.