Buzz by Block
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websitegithub.com Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Not listed
- Phone
- Not listed
- Command line
- Yes
- Agents
- Claude Code, Codex, Cursor Agent, OpenCode, Pi and Grok
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree and Container
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Yes
- Built-in issues
- Yes
- Pull requests
- Yes
- Review screen
- Yes
- Team
- Shared sessions and roles
- Self-hosting
- Yes
- Licence
- Apache-2.0
- Price from
- Free
- How it charges
- No paid plan and bring your own key
- Paid plans from
- Not listed
Receipts
- Checked
- · oldest answer 2026-11-07
- Findings
- 31 published · 26 cross-checked by a second agent · read them all
- Sources
- 27 public pages on 2 sites: api.github.com, github.com
- GitHub stars
- 33,254 on · api.github.com · repository attention, not users or capability
- Screenshot
- github.com, retrieved · first party repository · shows appearance, not capability
- Data
- /products/buzz.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Desktop downloads and CLI are documented; mobile remains under development.
Source and scope for Where you use itAgents it runs
Buzz documents ACP integration with named coding agents.
Source and scope for Agents it runsAccounts and subscriptions
Buzz desktop uses installed Claude and Codex native CLI authentication. Standalone buzz-acp documentation separately provides API-key setup examples, including a Codex API-key restriction for that route.
Source and scope for Accounts and subscriptionsWhere agents run
Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
Source and scope for Where agents runHow work is kept apart
The pinned release instructs coding agents to use Git worktrees and supplies container execution through its Kubernetes backend. Local worktrees are file separation; custom backend providers are outside the inspected built-in implementation.
Source and scope for How work is kept apartParallel work
Buzz documents a configurable ACP agent pool. No concurrency fixture was run.
Source and scope for Parallel workScheduled runs
Buzz documents relay-side cron, message, reaction and webhook workflows with bounded concurrency.
Source and scope for Scheduled runsGit and pull requests
Git event and hosting support is listed as working.
Source and scope for Git and pull requestsLicence and source
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
Source and scope for Licence and sourcePrice
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes cross-checked |
| Desktop OS: Windows | Yes cross-checked |
| Desktop OS: Linux | Yes cross-checked |
| Web client | Unknown |
| Phone access: Native iOS | No cross-checked |
| Phone access: Native Android | No cross-checked |
| Phone access: Phone browser | Unknown |
| CLI | Yes cross-checked |
| Coding agents: Claude Code | Yes cross-checked |
| Coding agents: Codex | Yes cross-checked |
| Coding agents: Cursor Agent | Yes cross-checked |
| Coding agents: Gemini CLI | Unknown |
| Coding agents: OpenCode | Yes cross-checked |
| Coding agents: Pi | Yes cross-checked |
| Coding agents: Grok | Yes cross-checked |
| Coding agents: Aider | Unknown |
| Coding agents: Antigravity | Unknown |
| Use my subscription | Yes |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | Unknown |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | Yes |
| Workspace isolation: VM or microVM | Unknown |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes |
| Native issue tracking | Yes cross-checked |
| Unattended triggers | Yes cross-checked |
| Shared prompting | Yes cross-checked |
| Team roles | Yes cross-checked |
| SSO | Unknown |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes cross-checked |
| Product license: Apache-2.0 | Yes. Apache-2.0 cross-checked |
| Product license: MIT | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: Elastic License 2.0 | No. Apache-2.0 cross-checked |
| Product license: Custom terms | No. Apache-2.0 cross-checked |
| Product license: Proprietary | No. Apache-2.0 cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Unknown |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Yes |
| Pricing model: Free plan | No |
| Pricing model: Subscription | No |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | Yes |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. Apache-2.0 cross-checked |
| Any desktop app | Yes cross-checked |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Unknown |
Filter receipts
Desktop OS: macOS: Yes cross-checked
Desktop OS: macOS
Typed value: Yes.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Desktop OS: Windows: Yes cross-checked
Desktop OS: Windows
Typed value: Yes.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Desktop OS: Linux: Yes cross-checked
Desktop OS: Linux
Typed value: Yes.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Phone access: Native iOS: No cross-checked
Phone access: Native iOS
Typed value: No.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Phone access: Native Android: No cross-checked
Phone access: Native Android
Typed value: No.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
CLI: Yes cross-checked
CLI
Typed value: Yes.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Coding agents: Claude Code: Yes cross-checked
Coding agents: Claude Code
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Harnesses: Goose, Codex and Claude Code.
- Session integration: ACP harness integration.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Coding agents: Codex: Yes cross-checked
Coding agents: Codex
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Harnesses: Goose, Codex and Claude Code.
- Session integration: ACP harness integration.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Coding agents: Cursor Agent: Yes cross-checked
Coding agents: Cursor Agent
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Custom adapters: Besides Goose, Codex and Claude Code, the desktop ships preset ACP entries for Pi, Devin, Cursor, Oh My Pi, Grok Build, OpenCode, Kimi, Amp, Hermes and OpenClaw; the user installs each CLI. Presets not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Buzz desktop preset harness catalog
Finding: The desktop ships preset ACP harness entries that launch user-installed CLIs, including Pi (through the buzz-pi-acp adapter), Cursor (cursor-agent acp), Grok Build (grok agent stdio) and OpenCode (opencode acp).
Coding agents: OpenCode: Yes cross-checked
Coding agents: OpenCode
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Custom adapters: Besides Goose, Codex and Claude Code, the desktop ships preset ACP entries for Pi, Devin, Cursor, Oh My Pi, Grok Build, OpenCode, Kimi, Amp, Hermes and OpenClaw; the user installs each CLI. Presets not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Buzz desktop preset harness catalog
Finding: The desktop ships preset ACP harness entries that launch user-installed CLIs, including Pi (through the buzz-pi-acp adapter), Cursor (cursor-agent acp), Grok Build (grok agent stdio) and OpenCode (opencode acp).
Coding agents: Pi: Yes cross-checked
Coding agents: Pi
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Custom adapters: Besides Goose, Codex and Claude Code, the desktop ships preset ACP entries for Pi, Devin, Cursor, Oh My Pi, Grok Build, OpenCode, Kimi, Amp, Hermes and OpenClaw; the user installs each CLI. Presets not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Buzz desktop preset harness catalog
Finding: The desktop ships preset ACP harness entries that launch user-installed CLIs, including Pi (through the buzz-pi-acp adapter), Cursor (cursor-agent acp), Grok Build (grok agent stdio) and OpenCode (opencode acp).
Coding agents: Grok: Yes cross-checked
Coding agents: Grok
Typed value: Yes.
Buzz documents ACP integration with named coding agents.
- Custom adapters: Besides Goose, Codex and Claude Code, the desktop ships preset ACP entries for Pi, Devin, Cursor, Oh My Pi, Grok Build, OpenCode, Kimi, Amp, Hermes and OpenClaw; the user installs each CLI. Presets not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Buzz desktop preset harness catalog
Finding: The desktop ships preset ACP harness entries that launch user-installed CLIs, including Pi (through the buzz-pi-acp adapter), Cursor (cursor-agent acp), Grok Build (grok agent stdio) and OpenCode (opencode acp).
Use my subscription: Yes
Use my subscription
Typed value: Yes.
Buzz desktop uses installed Claude and Codex native CLI authentication. Standalone buzz-acp documentation separately provides API-key setup examples, including a Codex API-key restriction for that route.
- Agent subscriptions: The desktop runtime catalog reuses authenticated installed Claude and Codex CLIs and their native login/status commands.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The desktop runtime catalog wraps installed Claude and Codex CLIs, instructs users to authenticate with the native Claude CLI or codex login, and probes claude auth status or codex login status. This differs from the API-key-only setup examples in the standalone buzz-acp README.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
- Local: just dev starts relay and desktop app together on the local machine.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Default relay is localhost:3000; packaged clients can switch relay. Source setup requires Docker and Hermit or the listed Rust/Node/pnpm toolchain. Production Compose supports a single-node VPS relay. Windows agent shell requires Git Bash or BUZZ_SHELL.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
- Byo remote: The bundled Kubernetes provider launches agent Pods in an operator-configured cluster.
- Client disconnect: The remote harness talks to the relay; the desktop does not maintain a management channel to the running process.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The bundled Kubernetes provider builds a Pod with one agent container, resource limits, a workspace volume and a non-root security context. This is a user-configured cluster, not a Block managed-compute service.
-
Finding: Desktop discovers buzz-backend provider executables, including the bundled Kubernetes provider. Remote harnesses use relay presence and shutdown messages without requiring a live desktop management connection. Custom providers can define other infrastructure.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
The pinned release instructs coding agents to use Git worktrees and supplies container execution through its Kubernetes backend. Local worktrees are file separation; custom backend providers are outside the inspected built-in implementation.
- Worktree: The shipped base prompt explicitly instructs file changes in a worktree, without enforcement.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The shipped agent prompt instructs agents to edit in a worktree and reuse an existing worktree when continuing work. It does not enforce or automatically provision a security boundary.
Workspace isolation: Container: Yes
Workspace isolation: Container
Typed value: Yes.
The pinned release instructs coding agents to use Git worktrees and supplies container execution through its Kubernetes backend. Local worktrees are file separation; custom backend providers are outside the inspected built-in implementation.
- Container: The Kubernetes provider creates an agent container in a Pod with its own workspace mount.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The bundled Kubernetes provider builds a Pod with one agent container, resource limits, a workspace volume and a non-root security context. This is a user-configured cluster, not a Block managed-compute service.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
Buzz documents a configurable ACP agent pool. No concurrency fixture was run.
- Concurrent sessions: buzz-acp spawns 1–32 agent subprocesses, default 1.
- Quotas: Pool configured from 1 to 32 subprocesses; workflow engine separately caps 100 active runs.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
Coordinator: Yes
Coordinator
Typed value: Yes.
Buzz supplies agent coordination through its shipped prompt and messaging CLI. Agents assign work to other running agents in the same channel and receive callback mentions with results; this does not imply automatic creation of an agent without owner approval.
- Roles: Any instructed Buzz agent can delegate work to existing agents through channel assignments.
- Messages: The shipped prompt defines notifying mentions and callback result messages using the Buzz CLI.
- Results return: Delegated work must return a result, deliverable or blocker with a notifying mention of the delegator.
- Orchestration owner: The base prompt and CLI messaging contract are supplied by Buzz.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz ships instructions for agents to delegate assignments to other running agents via channel mentions, requires results to mention the delegator, and supplies buzz messages send/get and signed agent identities.
Native issue tracking: Yes cross-checked
Native issue tracking
Typed value: Yes.
Human desktop and agent CLI use the same signed issue event model.
- Shared ids: Git issue event IDs in relay.
- Read: CLI get/list.
- Create: CLI and desktop publish signed issues.
- Assign: CLI assign/unassign.
- State changes: CLI status events.
- Attribution: Event signer.
- Conflicts: Prior assignment-head matching for constrained self-operations; wider conflict handling untested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
Buzz documents relay-side cron, message, reaction and webhook workflows with bounded concurrency.
- Schedules: Schedule triggers.
- Events: Message, reaction and webhook triggers.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Shared prompting: Yes cross-checked
Shared prompting
Typed value: Yes.
Buzz documents shared channels and threads with presence and membership boundaries.
- Coprompting: An agent's author gate can be set to an allowlist of team members or anyone, so several humans can instruct the same agent in a shared channel or thread. Default is owner-only.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The harness forwards events from its owner by default and can be set to an allowlist of team members or anyone, so several people can @mention and instruct the same agent in shared channels and threads.
Team roles: Yes cross-checked
Team roles
Typed value: Yes.
Buzz documents channel roles, authenticated membership and revocation operations. Enterprise SSO remains unknown.
- Organization roles: Relay-wide Operator and Moderator staff roles have a documented capability table in the moderation dashboard; channel roles are separate.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Buzz deployment moderation dashboard, principal model
Finding: Relay staff are resolved to Operator or Moderator roles with a documented capability table; only Operators manage the operator roster.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
Git event and hosting support is listed as working.
- Pull requests: Agents and people can open, update, list and set status on NIP-34 pull requests through the bundled buzz CLI; the desktop Projects preview adds create, review and merge controls.
- The desktop pull request UI sits in the opt-in Projects preview; pull requests are NIP-34 events on Buzz git hosting, not GitHub.
-
Finding: The desktop bundle ships buzz-acp, buzz-agent, buzz-backend-kubernetes and the buzz CLI as sidecar binaries.
-
buzz CLI pull request commands
Finding: The agent-facing buzz CLI can open, update, list and set status on git pull requests stored as NIP-34 events on the relay.
Review interface: Yes cross-checked
Review interface
Typed value: Yes.
Buzz marks canvases and media as working today.
- Diffs: The desktop Projects preview shows a files-changed diff panel for pull requests. Opt-in preview; not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Buzz desktop pull request files-changed panel
Finding: The desktop Projects view renders a files-changed diff panel for a pull request, beside create, review and merge controls.
-
Finding: Projects, the git repository browser and collaboration view, is listed as an opt-in desktop preview feature.
Product license: Apache-2.0: Yes. Apache-2.0 cross-checked
Product license: Apache-2.0
Typed value: Yes. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: MIT: No. Apache-2.0 cross-checked
Product license: MIT
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: GPL-3.0: No. Apache-2.0 cross-checked
Product license: GPL-3.0
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: AGPL-3.0: No. Apache-2.0 cross-checked
Product license: AGPL-3.0
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Elastic License 2.0: No. Apache-2.0 cross-checked
Product license: Elastic License 2.0
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Custom terms: No. Apache-2.0 cross-checked
Product license: Custom terms
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Proprietary: No. Apache-2.0 cross-checked
Product license: Proprietary
Typed value: No. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
Buzz can run a community on an operator-owned relay.
- Self hosting: Self-hostable relay workspace.
- Formats: Nostr signed-event format.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
Free access: Yes cross-checked
Free access
Typed value: Yes.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Ongoing free: The desktop app is a free Apache-2.0 download from GitHub releases.
- Paid only: Not paid-only: builds are downloaded free from the public release.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Free, no paid plan: Yes
Pricing model: Free, no paid plan
Typed value: Yes.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Free plan: No
Pricing model: Free plan
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Subscription: No
Pricing model: Subscription
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Bring your own key: Yes
Pricing model: Bring your own key
Typed value: Yes.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Model cost: Standalone buzz-acp supports user-supplied OpenAI and Anthropic API keys; provider charges are separate from Buzz.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
buzz-acp README, Codex and Claude Code
Finding: The Codex route requires an OpenAI API key and says not to use a ChatGPT subscription; the Claude Code route through claude-agent-acp is configured with an Anthropic API key.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Compute cost: Relays are self-hosted or deployed to Railway; hosting costs are not stated by Block.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
- Byo remote: The bundled Kubernetes provider launches agent Pods in an operator-configured cluster.
- Client disconnect: The remote harness talks to the relay; the desktop does not maintain a management channel to the running process.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Desktop discovers buzz-backend provider executables, including the bundled Kubernetes provider. Remote harnesses use relay presence and shutdown messages without requiring a live desktop management connection. Custom providers can define other infrastructure.
Open-source license: Yes. Apache-2.0 cross-checked
Open-source license
Typed value: Yes. Apache-2.0.
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- Client license: Apache-2.0, subject to component notices.
- Server license: The repository Apache-2.0 license applies to the relay source; component notices remain separate.
- Source visibility: Public repository.
- Source revision: 96af488d968a1ae9d961c2132bea27822735f8da
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Any desktop app: Yes cross-checked
Any desktop app
Typed value: Yes.
Desktop downloads and CLI are documented; mobile remains under development.
- Desktop os: macOS and Linux downloads, plus an unsigned Windows alpha build.
- Mobile apps: iOS/Android Flutter clients are in Being wired up, not released-store coverage.
- Cli: buzz-cli.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
buzz:ACC-01: Desktop downloads and CLI are documented; mobile remains under development. cross-checked
buzz:ACC-01
Desktop downloads and CLI are documented; mobile remains under development.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
buzz:ACC-02: Buzz documents ACP integration with named coding agents. cross-checked
buzz:ACC-02
Buzz documents ACP integration with named coding agents.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Buzz desktop preset harness catalog
Finding: The desktop ships preset ACP harness entries that launch user-installed CLIs, including Pi (through the buzz-pi-acp adapter), Cursor (cursor-agent acp), Grok Build (grok agent stdio) and OpenCode (opencode acp).
buzz:ACC-03: Buzz desktop uses installed Claude and Codex native CLI authentication. Standalone buzz-acp documentation separately provides API-key setup examples, including a Codex API-key restriction for that route.
buzz:ACC-03
Buzz desktop uses installed Claude and Codex native CLI authentication. Standalone buzz-acp documentation separately provides API-key setup examples, including a Codex API-key restriction for that route.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
buzz-acp README, Codex and Claude Code
Finding: The Codex route requires an OpenAI API key and says not to use a ChatGPT subscription; the Claude Code route through claude-agent-acp is configured with an Anthropic API key.
-
Finding: The desktop runtime catalog wraps installed Claude and Codex CLIs, instructs users to authenticate with the native Claude CLI or codex login, and probes claude auth status or codex login status. This differs from the API-key-only setup examples in the standalone buzz-acp README.
buzz:ACC-04: Buzz documents packaged-client, local source and VPS-relay setup prerequisites. Setup time was not measured. cross-checked
buzz:ACC-04
Buzz documents packaged-client, local source and VPS-relay setup prerequisites. Setup time was not measured.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Default relay is localhost:3000; packaged clients can switch relay. Source setup requires Docker and Hermit or the listed Rust/Node/pnpm toolchain. Production Compose supports a single-node VPS relay. Windows agent shell requires Git Bash or BUZZ_SHELL.
buzz:ACC-05: Buzz has agent CLI and signed WebSocket/REST programming interfaces. cross-checked
buzz:ACC-05
Buzz has agent CLI and signed WebSocket/REST programming interfaces.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
buzz:ACC-07: Desktop is Tauri with React; mobile Flutter remains unfinished. cross-checked
buzz:ACC-07
Desktop is Tauri with React; mobile Flutter remains unfinished.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: Pinned desktop build uses Tauri and React.
buzz:PLAN-01: Desktop and CLI create local relay-backed issue records. cross-checked
buzz:PLAN-01
Desktop and CLI create local relay-backed issue records.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
-
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
buzz:PLAN-06: Desktop creates issues with title, body and category. cross-checked
buzz:PLAN-06
Desktop creates issues with title, body and category.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
buzz:PLAN-07: Human desktop and agent CLI use the same signed issue event model. cross-checked
buzz:PLAN-07
Human desktop and agent CLI use the same signed issue event model.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
-
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
buzz:COORD-01: Buzz documents a configurable ACP agent pool. No concurrency fixture was run. cross-checked
buzz:COORD-01
Buzz documents a configurable ACP agent pool. No concurrency fixture was run.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:COORD-02: ACP dispatch queues channel mentions and claims agents from its pool. cross-checked
buzz:COORD-02
ACP dispatch queues channel mentions and claims agents from its pool.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:COORD-03: Buzz supplies agent coordination through its shipped prompt and messaging CLI. Agents assign work to other running agents in the same channel and receive callback mentions with results; this does not imply automatic creation of an agent without owner approval.
buzz:COORD-03
Buzz supplies agent coordination through its shipped prompt and messaging CLI. Agents assign work to other running agents in the same channel and receive callback mentions with results; this does not imply automatic creation of an agent without owner approval.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz ships instructions for agents to delegate assignments to other running agents via channel mentions, requires results to mention the delegator, and supplies buzz messages send/get and signed agent identities.
buzz:COORD-04: Buzz documents relay-side cron, message, reaction and webhook workflows with bounded concurrency. cross-checked
buzz:COORD-04
Buzz documents relay-side cron, message, reaction and webhook workflows with bounded concurrency.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:RUN-01: Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
buzz:RUN-01
Buzz runs agents locally or through user-configured backend providers. The bundled Kubernetes provider runs the harness in a user-controlled cluster; remote agents communicate through the relay independently of the desktop management process.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: Default relay is localhost:3000; packaged clients can switch relay. Source setup requires Docker and Hermit or the listed Rust/Node/pnpm toolchain. Production Compose supports a single-node VPS relay. Windows agent shell requires Git Bash or BUZZ_SHELL.
-
Finding: The bundled Kubernetes provider builds a Pod with one agent container, resource limits, a workspace volume and a non-root security context. This is a user-configured cluster, not a Block managed-compute service.
-
Finding: Desktop discovers buzz-backend provider executables, including the bundled Kubernetes provider. Remote harnesses use relay presence and shutdown messages without requiring a live desktop management connection. Custom providers can define other infrastructure.
buzz:RUN-02: The pinned release instructs coding agents to use Git worktrees and supplies container execution through its Kubernetes backend. Local worktrees are file separation; custom backend providers are outside the inspected built-in implementation.
buzz:RUN-02
The pinned release instructs coding agents to use Git worktrees and supplies container execution through its Kubernetes backend. Local worktrees are file separation; custom backend providers are outside the inspected built-in implementation.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: The bundled Kubernetes provider builds a Pod with one agent container, resource limits, a workspace volume and a non-root security context. This is a user-configured cluster, not a Block managed-compute service.
-
Finding: The shipped agent prompt instructs agents to edit in a worktree and reuse an existing worktree when continuing work. It does not enforce or automatically provision a security boundary.
buzz:RUN-03: The ACP harness detects crashed subprocesses and respawns them but does not persist its own state. cross-checked
buzz:RUN-03
The ACP harness detects crashed subprocesses and respawns them but does not persist its own state.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:RUN-05: Buzz documents workflow capacity rejection and expression timeouts. Agent spend limits remain unestablished. cross-checked
buzz:RUN-05
Buzz documents workflow capacity rejection and expression timeouts. Agent spend limits remain unestablished.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:RUN-06: Signed events and search supply activity records. cross-checked
buzz:RUN-06
Signed events and search supply activity records.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
buzz:RUN-08: ACP prompts queue per channel; workflows reject work at capacity instead of queueing. cross-checked
buzz:RUN-08
ACP prompts queue per channel; workflows reject work at capacity instead of queueing.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: buzz-acp runs 1–32 subprocesses, default one, queues mentions per channel with at most one prompt in flight, respawns crashed agents, and does not persist its state. Workflow concurrency is 100 permits and returns CapacityExceeded rather than queueing; cron evaluates every 60 seconds.
buzz:TEAM-01: Buzz documents shared channels and threads with presence and membership boundaries. cross-checked
buzz:TEAM-01
Buzz documents shared channels and threads with presence and membership boundaries.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
-
Finding: The harness forwards events from its owner by default and can be set to an allowlist of team members or anyone, so several people can @mention and instruct the same agent in shared channels and threads.
buzz:TEAM-02: Buzz documents channel roles, authenticated membership and revocation operations. Enterprise SSO remains unknown. cross-checked
buzz:TEAM-02
Buzz documents channel roles, authenticated membership and revocation operations. Enterprise SSO remains unknown.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
-
Buzz deployment moderation dashboard, principal model
Finding: Relay staff are resolved to Operator or Moderator roles with a documented capability table; only Operators manage the operator roster.
buzz:TEAM-03: Workflow approval gates are documented as incomplete and mark affected runs failed. cross-checked
buzz:TEAM-03
Workflow approval gates are documented as incomplete and mark affected runs failed.
- The README does not classify workflow approval gates as working today. No allow/deny scenario was run.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
buzz:TEAM-04: Buzz documents signed persisted events and a hash-chained append-only audit log. Retention guarantees remain unknown. cross-checked
buzz:TEAM-04
Buzz documents signed persisted events and a hash-chained append-only audit log. Retention guarantees remain unknown.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
buzz:SHIP-01: Buzz marks canvases and media as working today. cross-checked
buzz:SHIP-01
Buzz marks canvases and media as working today.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Buzz desktop pull request files-changed panel
Finding: The desktop Projects view renders a files-changed diff panel for a pull request, beside create, review and merge controls.
-
Finding: Projects, the git repository browser and collaboration view, is listed as an opt-in desktop preview feature.
buzz:SHIP-03: Git event and hosting support is listed as working. cross-checked
buzz:SHIP-03
Git event and hosting support is listed as working.
- The desktop pull request UI sits in the opt-in Projects preview; pull requests are NIP-34 events on Buzz git hosting, not GitHub.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
-
Finding: The desktop bundle ships buzz-acp, buzz-agent, buzz-backend-kubernetes and the buzz CLI as sidecar binaries.
-
buzz CLI pull request commands
Finding: The agent-facing buzz CLI can open, update, list and set status on git pull requests stored as NIP-34 events on the relay.
-
Buzz desktop pull request files-changed panel
Finding: The desktop Projects view renders a files-changed diff panel for a pull request, beside create, review and merge controls.
-
Finding: Projects, the git repository browser and collaboration view, is listed as an opt-in desktop preview feature.
buzz:OWN-01: Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices. cross-checked
buzz:OWN-01
Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
buzz:OWN-02: Buzz can run a community on an operator-owned relay. cross-checked
buzz:OWN-02
Buzz can run a community on an operator-owned relay.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
buzz:OWN-03: Buzz documents local/operator-owned data stores and signed-key authentication. Telemetry and model training policy remain unknown. cross-checked
buzz:OWN-03
Buzz documents local/operator-owned data stores and signed-key authentication. Telemetry and model training policy remain unknown.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Channel membership roles are Owner, Admin, Member, Guest and Bot, with transactional member/channel operations and soft removal. NIP-42 and NIP-98 authenticate signed events. Audit is append-only SHA-256 hash chained, excludes ephemeral events, and can verify chains. Approval workflow gates are not wired end to end.
buzz:OWN-04: Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
buzz:OWN-04
Buzz desktop and relay are distributed under a no-charge Apache-2.0 license with no paid Buzz tier in the checked README and release. Users pay their infrastructure and agent providers separately; standalone agent examples accept model-provider API keys.
- Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
-
Finding: Buzz is a self-hostable workspace; a relay can be self-run or deployed to Railway via a one-click button, with no Buzz price stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
-
buzz-acp README, Codex and Claude Code
Finding: The Codex route requires an OpenAI API key and says not to use a ChatGPT subscription; the Claude Code route through claude-agent-acp is configured with an Anthropic API key.
buzz:OWN-06: README explicitly separates working, unfinished and vision capabilities. cross-checked
buzz:OWN-06
README explicitly separates working, unfinished and vision capabilities.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Working table lists relay, desktop Tauri/React, CLI/ACP, signed Git events and YAML event/schedule workflows. Mobile and workflow approval gates remain unfinished; vision prose is separate.
buzz:OWN-08: Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate. cross-checked
buzz:OWN-08
Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.
- Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.
-
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.