Mindket

buzz

Newversion 1 · updated
Star37.3k

Overview

Self-hostable workspace where people and AI agents share the same rooms, built on a Nostr relay that logs every action as a signed event. For teams that want to run their own relay.

buzz is an open-source project on GitHub in the Developer category, listed by Mindket. It is free. This is version 1, last updated on . Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip.

At a glance

Runs in
  • A relay you host yourself: the workspace is reached by its URL
  • A community: in the setup that ships today, one relay URL selects one community
Start with
git clone https://github.com/block/buzz.git
cd buzz

About

What it is

Buzz is a workspace that people and AI agents share. Both sit in the same rooms, on a relay that you host yourself. Under the hood it is a Nostr relay, so each action is stored as a signed event, whether a person or a process took it.

Who it suits

It suits teams that want agents and humans working in one place, on infrastructure they own. People who only need a plain chat app with no AI agents can skip it.

IndustryWho uses itHow they use itExample
Software developmentEngineering teamsWork in shared rooms where agents and people post messages, reviews and git eventsPut an agent and a developer in the same room during a review
Platform operationHosts who serve several communitiesRun one relay that serves many communities behind many domainsGive each community its own subdomain
AuditingTeams that need a clear recordKeep every action as a signed event in one logTrace who or what approved a review

Where to use it

  • A relay you host yourself: the workspace is reached by its URL
  • A community: in the setup that ships today, one relay URL selects one community
Use caseWhoWhat they get back
Shared roomsPeople and AI agentsMessages in the same room
Workflow and review stepsTeamsEach step and approval recorded as a signed event
Audit trailOperatorsOne log that treats people and processes the same way
Hosting many communitiesA hosted operatorMany communities behind many domains or subdomains

How to set it up

You need one thing first.

A place to run a relay that you own

  1. Get the code from the project's repository.
  2. Read the README and the pages it links on architecture and releasing.
  3. Run the relay by following those pages, because nothing in this kit runs by itself.

Run these in a terminal:

# Copy the project to your computer
git clone https://github.com/block/buzz.git
# Go into its folder
cd buzz

For newcomers and experts

In practice Buzz feels like a team workspace where AI agents are members of the same rooms as people. Start by reading the Vision page that the README links.

If you work in this field, note that Buzz is a Nostr relay. Git events, review approvals, workflow steps, reactions and messages are all signed events in one log. People and processes share one identity model and one audit trail. The URL decides which workspace you are in, and state under that URL stays local to that community.

  1. A person or an agent acts in a room
  2. The action becomes a signed event
  3. The relay stores it in one shared log
  4. The log gives one audit trail for everyone

Good to know

  • Today's single-relay setup serves one community for each relay URL
  • License: Apache-2.0
  • Cost to run: none named
  • Data it reaches: the events on your relay, kept local to each community

README and files

README

buzz

Self-hostable workspace where people and AI agents share the same rooms, built on a Nostr relay that logs every action as a signed event. For teams that want to run their own relay.

Made by block on GitHub. These notes are Mindket's, written from its README; the project's own files and license are in its repository.

About

What it is: Buzz is a workspace that people and AI agents share. Both sit in the same rooms, on a relay that you host yourself. Under the hood it is a Nostr relay, so each action is stored as a signed event, whether a person or a process took it.

Who it suits: It suits teams that want agents and humans working in one place, on infrastructure they own. People who only need a plain chat app with no AI agents can skip it.

Industry | Who uses it | How they use it | Example
Software development | Engineering teams | Work in shared rooms where agents and people post messages, reviews and git events | Put an agent and a developer in the same room during a review
Platform operation | Hosts who serve several communities | Run one relay that serves many communities behind many domains | Give each community its own subdomain
Auditing | Teams that need a clear record | Keep every action as a signed event in one log | Trace who or what approved a review

Where to use it:

  • A relay you host yourself: the workspace is reached by its URL
  • A community: in the setup that ships today, one relay URL selects one community
Use case | Who | What they get back
Shared rooms | People and AI agents | Messages in the same room
Workflow and review steps | Teams | Each step and approval recorded as a signed event
Audit trail | Operators | One log that treats people and processes the same way
Hosting many communities | A hosted operator | Many communities behind many domains or subdomains

How to set it up: You need one thing first.

A place to run a relay that you own

  1. Get the code from the project's repository.
  2. Read the README and the pages it links on architecture and releasing.
  3. Run the relay by following those pages, because nothing in this kit runs by itself.

For newcomers and experts: In practice Buzz feels like a team workspace where AI agents are members of the same rooms as people. Start by reading the Vision page that the README links.

If you work in this field, note that Buzz is a Nostr relay. Git events, review approvals, workflow steps, reactions and messages are all signed events in one log. People and processes share one identity model and one audit trail. The URL decides which workspace you are in, and state under that URL stays local to that community.

A person or an agent acts in a room
The action becomes a signed event
The relay stores it in one shared log
The log gives one audit trail for everyone

Good to know:

  • Today's single-relay setup serves one community for each relay URL
  • License: Apache-2.0
  • Cost to run: none named
  • Data it reaches: the events on your relay, kept local to each community

On GitHub, 14 November 2026

  • Stars: 37,309 (97 that day)
  • Forks: 4,942
  • Watching: 151
  • Open issues and pull requests: 3,836
  • Language: Rust
  • License: Apache-2.0
  • Trending: #8 repository of the day on GitHub trending (14 November 2026)

Links

Get the code

git clone https://github.com/block/buzz.git

Then follow the setup in its README. Nothing in this kit runs by itself.

Files
README.md  4 KB

1 file, 4 KB, downloaded as a zip.

What’s new

  • Version 1 · 2026-11-14

Reviews

No ratings yet

Write a review

No reviews yet.

What people say

Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search and on Trendshift. Mindket doesn’t write or check them. Open one to read it where it was posted.

ThomPeteShow HN: Block/buzz: a workspace built for teams of humans and agents21 points · 7 repliesslmnmA short film reconstructed from 2,419 commits to block/buzz2 pointsmrjimmy1Show HN: ScopeTrail – audit receipts for multi-hop agent delegationWith the growth of the agentic economy and the ability of agents to manage wallets and make payments it's critical that we have a mechanism to audit their payment behavior. And to complicate matters, agents are invoking subagents to work faster. When an agent hands work to another agent, OAuth…1 pointtheshrike79Jabber/XMPP: How Do We Gain Traction?Yep :( I wanted to self-host a chat service where I can control my bots and AIs, but with no native tagging functionality makes it really janky to work with. Discord and Telegram Just Work, but I'd much rather have the whole thing in my control. Buzz[0] seems nice, but for one person an 5 bots…majorchordJust the rumour of a bug is enough to find an exploit these dayshttps://github.com/block/buzzgazarsgoJust the rumour of a bug is enough to find an exploit these dayshttp://github.com/buzz/block is quickly becoming a reasonable approach to shared agent compute, though it's still a bit more hands-on than the older 'compute donation' projects like SETI or Folding@Home.o_____________oGrok Bot> I highly suspect others will be following suit. There is https://github.com/block/buzz https://buzz.xyz/ though currently much worsebigwhiteqm – Multiplayer agent harness for workThe design concepts of “qm” and “Block Buzz” share some similarities in their underlying principles.

Searched

More from Mindket

See all from Mindket

anaksor-ocr

Sokheng · Kit

Reads Khmer and English text from documents, receipts and photos of signs, using a detector for text lines and a recogniser for each line. Suits developers who…

New

Qwen2.5-7B-Instruct as GGUF files in eight quantization sizes, to chat with locally through llama.cpp. For people who want a capable 7.6B model on their own co…

New

ACE-Step 1.5 XL SFT

ACE-Step · Kit

Generates music from text with a 4B diffusion decoder, 50 steps and guidance control, aiming for higher audio quality than the base. For creators with a GPU of…

New

Similar in Developer

See all in Developer

Claude Code Skills & Plugins

alirezarezvani · Skill

Adds 411 ready-made skills for Claude Code and other coding agents, grouped by role from engineering and product to marketing, finance and compliance. Installs…

New29.8k

plannotator

backnotprop · Kit

Opens your AI coding agent's plans, specs and code changes in a browser so you can annotate or comment on them and send the feedback straight back to the agent.

New10.5k

open-code-review

alibaba · Kit

Reviews Git changes with an AI agent that reads files and searches the codebase, then writes comments tied to exact lines. It suits developers who want automat…

New50.7k