# Buzz by Block

34 Hacker News commenters recommended Buzz by Block and 29 criticized it, November 2025 to November 2026. It was recommended in 8 of 13 months.

**Verdict:** Recommended as a team workspace combining chat, AI agents and code, with channels that serve as shared memory. Critics say it is too agent-focused and complex for its needs.

## Why people recommend it

- Teams and agents collaborating in one place (5 comments): "The channel as memory has been a big help on larger features that span multiple engineers and many agent sessions." ([source](https://news.ycombinator.com/item?id=48633858)) "I also really love Buzz's vision for team collaboration with many humans and many bots" ([source](https://news.ycombinator.com/item?id=49282200)) "I think this is a good way to do dev together with teams and agents going forward." ([source](https://news.ycombinator.com/item?id=48632992))
- Seen as the future of work (3 comments): "This is basically the ide of the future if you think about it." ([source](https://news.ycombinator.com/item?id=48998109)) "Buzz looks like a more reasonable direction than this does." ([source](https://news.ycombinator.com/item?id=49183527)) "Buzz seems like the future." ([source](https://news.ycombinator.com/item?id=48633758))
- Open, self-hosted, decentralized approach (2 comments): "Excited for "decentralized, self-sovereign, and open source." Indifferent to "groupchat for agents"." ([source](https://news.ycombinator.com/item?id=48996474)) "Self-hosted stuff looks appealing to me." ([source](https://news.ycombinator.com/item?id=48997197))
- Ambitious, well-refactored codebase (2 comments): "it's been refactored and improved a lot, so it isn't your average vibecoded project" ([source](https://news.ycombinator.com/item?id=48052158)) "admire them for thinking differently and trying to build something interesting" ([source](https://news.ycombinator.com/item?id=49001175))

## What people warn about

- Unclear fit for software teams (3 comments): "It's hard to imagine incrementally adopting this." ([source](https://news.ycombinator.com/item?id=48996141)) "Interesting idea. Biggest problem is that I do think most companies have a ton of key contributors that find git/code intimidating" ([source](https://news.ycombinator.com/item?id=48996465)) "I'm trying to imagine a world in which this makes sense as a way to organize software development work, but coming up short." ([source](https://news.ycombinator.com/item?id=48996595))
- Overbuilt infrastructure and Nostr layer (3 comments): "for one person an 5 bots having a full-ass postgres+redis+s3 setup seems completely bonkers" ([source](https://news.ycombinator.com/item?id=49708316)) "it was way too complicated with Nostr and a bunch of things that are way too much for what I intend to use it for" ([source](https://news.ycombinator.com/item?id=50090951)) "with this Nostr layer that doesn’t really provide any specific value that I can see" ([source](https://news.ycombinator.com/item?id=48997102))
- Google Buzz fiasco associations (2 comments): "the company that insisted on learning the wrong things from the Google Buzz fiasco" ([source](https://news.ycombinator.com/item?id=48021079)) "they also fucked up by trying to leverage Gmail into Google Buzz" ([source](https://news.ycombinator.com/item?id=50012948))
- Unresolved auth, bot and git design (3 comments): "they 'invented' an auth and permission protocol instead of delegating to something existing" ([source](https://news.ycombinator.com/item?id=48997275)) "Does everyone get a bot? If people share one, whose credentials does it use?" ([source](https://news.ycombinator.com/item?id=48998741)) "I also am curious whether git really needs to be a dependency here." ([source](https://news.ycombinator.com/item?id=48997954))

## Cite as

Hacker Approved, "Buzz by Block", https://hackerapproved.com/p/buzz/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).