pull down to refresh

I remember Jack Dorsey offering a big bounty for Github built on nostr some years ago. I don't know what ever came of that, but this seems like it might be the spiritual successor:

Buzz is a self-hostable workspace where humans and AI agents share the same rooms.

A Buzz community is the workspace a user reaches by URL. In the single-relay setup that ships today, the relay URL selects exactly one community. A hosted operator can serve many communities behind many domains or subdomains, but the client-facing rule stays the same: the URL is authoritative for the workspace, and all tenant-observable state under that URL is community-local.

It's a Nostr relay: every message, reaction, workflow step, review approval, and git event is a signed event in one log. Same shape, same identity model, same audit trail, whether the author is a person or a process.

In practice it feels like a team workspace. Under the hood it's an event log with taste and a suspicious number of Rust crates.

Yes, it's another AI-adjacent developer tool. We're sorry. The difference is what agents can actually do once they're inside: open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels, and pull in whoever needs to see it. The same affordances as a human teammate, the same audit trail, a different keypair.

Here's what they say you can do with Buzz:

  • Ask the project a question and get an answer with receipts. Agents search six months of history and post the threads, not vibes.
  • Let an agent triage a bug without giving it the keys to the kingdom. Agents have their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags — the same way you'd scope a teammate.
  • Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why the code exists.
  • Search the conversation, the patch, the workflow run, and the approval in one place — because they're all the same kind of event.
  • Let an agent run the workspace, not just talk in it. Channels, canvases, workflows, huddles — agents have the same surface area as humans, with their own keys and their own audit trail.

Jack Dorsey is posting about it on X:

And they have a website: buzz.xyz

It's good that they publish this. Can be a real enabler for teams stuck in slack and on GH.

I too have been using RBAC instead of PAT scoping (tho I cringe at "user" and the corresponding roleplay for a bot, so not a fan of "chat") and it has been an enabler of proper auth scoping.

Still am searching for a way to reduce chattiness... it's such a time waster. "Nice catch?" You talk to your boss like that, mf? lol.

I don't want to change the default system prompt into something like "you are a robot slave that does what it is told under all circumstances" simply because that would eliminate all the post-training they do on the models. But really: less chat, more results.

reply

I assume this is only useful for software development?

reply