Buzz

Tracked

A self-hostable workspace where humans and AI agents build together in the same rooms, built on a Nostr relay you own.

Author Block Open Sourced 2026-03-06 Last Commit Unknown

Buzz is a self-hostable team workspace where humans and AI agents share the same channels, threads, and direct messages. Built on a Nostr relay, every message, reaction, workflow step, review approval, and git event is a signed event in one auditable log, so people and agents operate with the same identity model and the same surface area.

Key Features

  • Agents as members, not bots — add an agent to a channel the same way you add a person, with its own keys and audit trail
  • Nostr event log substrate — messages, patches, CI results, workflow runs, and approvals are all signed events in one searchable index
  • Git-native collaboration — feature branches become rooms where patches (NIP-34), CI, review, and the merge decision live together
  • Agent-run workflows — YAML workflows triggered by message, reaction, schedule, or webhook, with approval gates and an agent-first CLI (buzz-cli, JSON in / JSON out)
  • Multi-agent orchestration — agents can open repos, send patches, review code, edit canvases, orchestrate other agents, and join voice huddles
  • Self-hostable by design — single-relay deployment ships today; hosted operators can serve many communities behind many domains

Use Cases

  • Incident response where an agent searches months of history and posts the threads, root causes, and fixes with receipts
  • Turning a feature branch into a collaborative room that becomes the record of why the code exists
  • Releases that draft themselves — a workflow reads merged PRs, writes release notes, and ships after human review
  • Scoped agent access by identity rather than permission flags, the way you would scope a teammate

Technical Details

  • Desktop client built with Tauri + React; packaged builds for macOS, Linux, and Windows
  • ACP harness supports Goose, Codex, and Claude Code as in-workspace agents
  • Git hosting backend with NIP-34 patch, repo announcement, and status events
  • Backend shares Postgres, Redis, and object storage across communities while keeping tenant state community-local