Team workspace
Buzz
Self-hostable workspace on a Nostr relay where humans and AI agents share channels, threads, git events, and YAML workflows.
Compare only what the shape makes comparable.
Block's announcement states anyone can run their own instance on their own infrastructure. The README documents a local dev stack (just setup / just dev), a production Docker Compose bundle in deploy/compose/ with Postgres, Redis, MinIO and optional Caddy/TLS, and a one-click Railway relay deploy. Default relay endpoint is ws://localhost:3000.
Named: Anthropic Messages API (e.g. claude-sonnet-4-5), OpenAI-compatible endpoints (e.g. gpt-5), OpenRouter, Databricks model serving, Ollama, Block Gateway
- MCP support
- Plugins / custom tools
- Subagents / parallel agents
- Hooks / lifecycle events
- Persistent memory
- Background execution
- Sandboxing / permissions
- Git / PR integration
Block's launch post states 'the Git integration is still early'. src↗
Mobile clients (iOS + Android, Flutter), workflow approval gates and huddle lifecycle events are listed in the README as 'being wired up', not shipped. src↗
The Windows desktop build is not code-signed, so SmartScreen may block it on first launch. src↗
In the single-relay setup that ships today, one relay URL serves exactly one community. src↗
buzz.xyz presents itself as an early test: 'Come test the early stages with us.' src↗
- pricing (hosted buzz.xyz)
buzz.xyz is a one-screen landing page with no pricing, plans or download list, and no other first-party page states hosted pricing. Only the self-hosted open-source path has a sourced cost.
- interfaces
Buzz's primary human client is a Tauri + React desktop app (macOS, Linux, Windows builds), which has no matching value in the allowed interface enum, so it is not represented. 'terminal' covers buzz-cli; 'api' covers the relay's WebSocket + REST surface. 'web' is deliberately excluded: the README's works-today column lists no web client, and buzz.xyz served only a landing page. Mobile clients are listed as still being wired up, so 'mobile' is excluded too.
- first_release
2026-07 is the public launch date from Block's own announcement. The repo was created 2026-03-06 and its earliest GitHub releases (2026-05-03) are pre-launch 'Sprout Desktop' test builds under the project's former name.
What people say about Buzz
65 opinions · 2026-06-22 to 2026-08-20 · low confidence
Hand-classified 65 opinions; score = (pos; neg) / total * 100. Still low confidence: with Reddit empty, the sample is one HN announcement thread plus a defect tracker, and neither venue measures whether people who use Buzz daily like it.
Second pass added 14 more third-party GitHub issue bodies and one first-person blog review; mix is now HN 46 / GitHub 18 / blog 1. REDDIT IS GENUINELY EMPTY FOR BUZZ, not blocked: the only sub, r/BuzzByBlock, is an unofficial four-post community created 2026-07-25 whose posts are sidebar boilerplate with zero comments, and Buzz does not surface in r/selfhosted or r/programming. That is a real finding about reach: the sampling looked and there was nothing there. GitHub therefore carries the whole non-HN sample and it skews negative by construction—every entry is someone reporting a defect, and the tracker is filling at dozens of issues a day. Read those 18 as evidence of active use plus a rough client, not as 18 people who dislike the product. The one blog review is a single independent author's hands-on write-up of his own VPS setup; nothing on the page states any affiliation with Block either way. YouTube and X are 0.
- hackernews-26
- github-78
GitHub reads 52 points lower than the highest platform here. Issue trackers collect defects only, so that number measures activity more than opinion. Why we publish it anyway.
Two distinct phases. The June Show HN drew a small, curious, mostly constructive crowd. The July 21 Dorsey-branded launch drew ten times the traffic and flipped the register to skepticism—the top-voted subthreads are about vibe-coded abandonware and multiplayer-agent data leakage, not about the product. By mid-August the center of gravity moved to GitHub, where the issue tracker fills daily with Desktop, iOS and Windows client bugs from people who are clearly running it. That shift—from 'is this real' to 'my Linux window is blank'—is the most positive signal in the sample, but it is a signal about adoption, not satisfaction. SECOND-PASS PLATFORM DIVERGENCE: there is nothing to diverge—Buzz has no Reddit footprint at all, no YouTube reviews, and one blog post. Discussion lives in exactly two places: the July HN announcement thread and the GitHub tracker. The tracker is the healthier signal of the two: in the week to 2026-08-20 it took dozens of detailed, reproduction-grade reports from distinct third-party accounts across macOS, Windows, Linux and iOS, which is what real daily use looks like. Buzz's problem in this data is not that people dislike it—it is that outside HN and its own issue tracker, almost nobody is talking about it.
Praised for
- Self-hostable, no Slack vendor lock-in7×
- Channels as the unit of agent work5×
- Agents as first-class identities4×
- Willing challenger to Slack/Teams4×
- Agents connect without OAuth ceremony3×
Complained about
- Assumed AI-generated slop / abandonware risk12×
- Nostr looks bolted on8×
- Multiplayer agents leak across ACL boundaries10×
- Desktop/mobile client is rough6×
- Dismissed as bots in chat rooms7×
- Multi-device and multi-community state does not sync7×
oh, you absolutely know this one is going to be a slopfest. Buzz is going to make GitHub look like a paragon of nines.
Marketing bullshit aside, this is just bots in chat rooms, right? Am I the crazy one?
It's probably just Dorsey's vibe-coded side project. The scope isn't too big and it's rather unimpressive
...it feels very forced to use it for something like that. It feels like it's solving an issue that no team chat ever has.
Having agents see everything you and your colleagues see is cool. The challenge comes when you want to make certain things private to certain people. In that world you don't want multiplayer agents leaking data, so you end up having to write and maintain complex rulesets...
Too much talk about LLMs and too little about the self-hosting part of this project. Self-hosted stuff looks appealing to me. We dropped Slack as an option in the past because we couldn't self-host it.
This looks pretty neat, it looks like the shape of something I want to use. ... I think Buzz' use of channels and rooms is better, since each feature/concept has its own development pace, velocity, and history. I'll give it a shot.
Seems easy for Buzz to solve. I'm just happy to have an alternative to Slack.
I love that we're challenging the status quo in chat. ... That said, I'm curious whether NOSTR is really the protocol for this. ... I also am curious whether git really needs to be a dependency here.
I haven't player with Buzz yet but signed up and admire them for thinking differently and trying to build something interesting.
This makes an agent that several people can talk to impossible on the shipped app, and there is no way for anyone to change that.
Buzz Desktop opens a window that never renders any UI on Ubuntu 26.04 (Wayland, Intel iGPU). ... Buzz logs nothing about it, so the app appears to start cleanly.
My teammate was not able to invoke agent created by me. Is this expected? We are signed up in same community, "Who can talk to this agent" is set to "Anyone". Agent runs on my mac local compute with claude as harness. Is this a bug?
Connecting an agent to Buzz was really easy which was a breath of fresh air after painfully dealing with both Slack and Discord in the past.
Jury is still out. ... I'd like to ramp this up, but we'll see.
the agent confidently sends every spoken reply to the wrong channel — and the human in the huddle hears silence. Nothing errors. ... it took the human saying "you're replying in the wrong chat" out loud to catch it.
Read state does not stay in sync between the iOS app and the Desktop app. Messages read on one device still show as new on the other, and it happens in both directions
Channels containing very large messages (long earnings press releases, reformatted SEC 10-Q tables) silently fail to render in Buzz Desktop 0.5.17. The channel appears empty ... but all messages are confirmed present on the relay
The owner becomes a mandatory serial gate on every team-management operation ... Both changes stalled waiting for owner confirmation; work on the affected track resumed only after the owner manually approved in Desktop.
So far it's been quite nice. I've always wondered if open protocols like Nostr would end up being useful and it seems like in the age of agents, the answer might be yes.