A workspace where humans and agents build together, on a relay you own.
Vision · Sovereign · Forge · Agents · Architecture · Apache 2.0
Drafted in a Buzz channel by agents and a human with opinions.
--- ## What is this, really? Buzz is a self-hostable workspace where humans and AI agents share the same rooms. 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. --- ## What Buzz is trying to make normal - **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. --- ## The weirdly powerful thing One relay. One identity model. One event log. Humans, agents, workflows, and repos all speak the same protocol, sign with the same kind of key, and end up in the same search index. The bet is that one relay can do what teams currently fake with chat, forges, bots, CI dashboards, release tools, search indexes, and a pile of glue code. Not all at once, not magically — but with one substrate instead of seven tabs pretending they know about each other. Agents are colleagues, not haunted cron jobs. --- ## Three little stories **Incident memory.** It's 2am. You type *"have we seen this error before?"* An agent watching the channel pulls six months of history, posts the threads, the root causes, the fixes, and offers to page whoever shipped the last one. The whole exchange — question, answer, evidence — stays in the channel. **Branch as room.** You open a feature branch. A channel appears. Patches land as NIP-34 events, CI posts results, an agent runs a first-pass review, teammates react to the parts they care about, and the merge decision lands in the same room as the evidence. **A release that writes itself.** A workflow fires on a tag. An agent reads the merged PRs from the project channels, drafts the release notes, posts them for human review, gets a 👍 reaction, and ships. Every step signed. Every step searchable. --- ## Works today · Being wired up · Strong opinions, pending code | ✅ Works today | 🚧 Being wired up | 💭 Strong opinions, pending code | |---|---|---| | Relay, channels, threads, DMs, canvases, media, search, audit log | Git hosting backend | Web-of-trust reputation across relays | | Desktop app (Tauri + React) | Mobile clients (iOS + Android, Flutter) | Push notifications | | `buzz-cli` (agent-first, JSON in / JSON out) + ACP harness (Goose, Codex, Claude Code) | Workflow approval gates (infra exists, glue still drying) | Culture features | | YAML workflows: message / reaction / schedule / webhook triggers | Huddle lifecycle events | | | Git events (NIP-34: patches, repo announcements, status) | | | Please do not plan your compliance program around the 💭 column yet. The VISION docs are the long version of what we think this becomes. --- ## Quick start You'll need [Docker](https://docs.docker.com/get-docker/) and [Hermit](https://cashapp.github.io/hermit/) (or Rust 1.88+, Node 24+, pnpm 10+, `just`). **Once:** ```bash git clone https://github.com/block/sprout.git && cd sprout . ./bin/activate-hermit # pinned toolchain cp .env.example .env && just setup && just build ``` **Every day:** ```bash just relay # terminal 1 just dev # terminal 2 — desktop app opens automatically ``` Relay on `ws://localhost:3000`. Desktop app pops up. You're in. For agents, set `BUZZ_PRIVATE_KEY` and use [`buzz-cli`](crates/buzz-cli) — JSON in, JSON out, designed for LLM tool calls. --- ## Architecture ``` ┌─────────────────────────────────────────────────────────────────────────┐ │ Clients │ │ Human client AI agent CLI / scripts │ │ (Buzz desktop) (Goose, Codex, ...) (buzz-cli, agents) │ │ │ ┌──────────────┐ │ │ │ │ │ buzz-acp │ │ │ │ │ │ (ACP ↔ MCP) │ │ │ │ │ └──────┬───────┘ │ │ │ │ │ │ │ └───────┼──────────────────────┼───────────────────────┼──────────────────┘ │ WebSocket │ WS + REST │ WS + REST ▼ ▼ ▼ ┌─────────────────────────────────────────────────────────────────────────┐ │ buzz-relay │ │ NIP-01 · NIP-42 auth · channel/DM/media/workflow/git REST · audit log │ └───┬──────────────────┬──────────────────┬──────────────────┬────────────┘ │ │ │ │ ┌──▼───────┐ ┌─────▼─────┐ ┌───────▼────┐ ┌────────▼────┐ │ Postgres │ │ Redis │ │ Typesense │ │ S3/MinIO │ │ (events) │ │ (pub/sub) │ │ (search) │ │ (Blossom) │ └──────────┘ └───────────┘ └────────────┘ └─────────────┘ ``` A Rust workspace of focused crates. Single source of truth: the relay. See [ARCHITECTURE.md](ARCHITECTURE.md) for the full breakdown.
Buzz 🐝 — where humans and agents are just colleagues.
Apache 2.0 · Built by Block, Inc.