# Buzz by Block

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/buzz/
Website: https://github.com/block/buzz
Research: covered

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## buzz:ACC-01

Finding: Desktop downloads and CLI are documented; mobile remains under development.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI; Buzz mobile clients
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

## buzz:ACC-02

Finding: Buzz documents ACP integration with named coding agents.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src-tauri/src/managed_agents/discovery/presets.rs#L106-175
Locator: desktop/src-tauri/src/managed_agents/discovery/presets.rs lines 106-175 (PRESET_HARNESSES), release tag desktop-v0.5.28 (commit f87c108)
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).
Retrieved: 2026-11-10

## buzz:ACC-03

Finding: 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.

Verification: sourced
Checked: 2026-11-10
Scheduled recheck: 2026-12-10
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: Not specified

Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-acp/README.md#L72-104
Locator: crates/buzz-acp/README.md lines 72-104 (Running with Codex, Running with Claude Code), release tag desktop-v0.5.28 (commit f87c108)
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.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src-tauri/src/managed_agents/discovery/catalog.rs
Locator: KnownAcpRuntime Claude and Codex, lines 51-120
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.
Retrieved: 2026-11-13

## buzz:ACC-04

Finding: Buzz documents packaged-client, local source and VPS-relay setup prerequisites. Setup time was not measured.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Getting started; Quick start; Windows prerequisites
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.
Retrieved: 2026-11-07

## buzz:ACC-05

Finding: Buzz has agent CLI and signed WebSocket/REST programming interfaces.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/crates/buzz-cli/src/commands/issues.rs
Locator: cmd_create_issue; cmd_issue_status; assignment reducer
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

## buzz:ACC-07

Finding: Desktop is Tauri with React; mobile Flutter remains unfinished.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2027-02-05
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI; Buzz mobile clients
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/desktop/package.json
Locator: Tauri scripts; React dependency
Finding: Pinned desktop build uses Tauri and React.
Retrieved: 2026-11-07

## buzz:PLAN-01

Finding: Desktop and CLI create local relay-backed issue records.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/crates/buzz-cli/src/commands/issues.rs
Locator: cmd_create_issue; cmd_issue_status; assignment reducer
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/desktop/src/features/projects/issueMutations.ts
Locator: publishProjectIssue; useCreateProjectIssueMutation
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
Retrieved: 2026-11-07

## buzz:PLAN-06

Finding: Desktop creates issues with title, body and category.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/desktop/src/features/projects/issueMutations.ts
Locator: publishProjectIssue; useCreateProjectIssueMutation
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
Retrieved: 2026-11-07

## buzz:PLAN-07

Finding: Human desktop and agent CLI use the same signed issue event model.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/crates/buzz-cli/src/commands/issues.rs
Locator: cmd_create_issue; cmd_issue_status; assignment reducer
Finding: CLI creates, reads, lists, changes issue status and publishes signed assignment events. Prior assignment-head checks constrain self operations.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/desktop/src/features/projects/issueMutations.ts
Locator: publishProjectIssue; useCreateProjectIssueMutation
Finding: Desktop signs and publishes the shared Git issue event with title/body/category and refreshes project issue queries.
Retrieved: 2026-11-07

## buzz:COORD-01

Finding: Buzz documents a configurable ACP agent pool. No concurrency fixture was run.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:COORD-02

Finding: ACP dispatch queues channel mentions and claims agents from its pool.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:COORD-03

Finding: 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.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: Not specified

Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-acp/src/base_prompt.md
Locator: Communication patterns > Callback mentions and Threading; Buzz CLI
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.
Retrieved: 2026-11-13

## buzz:COORD-04

Finding: Buzz documents relay-side cron, message, reaction and webhook workflows with bounded concurrency.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:RUN-01

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Getting started; Quick start; Windows prerequisites
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-backend-kubernetes/src/pod.rs
Locator: Pod construction, lines 108-175; desktop/src-tauri/tauri.conf.json externalBin
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.
Retrieved: 2026-11-13

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src-tauri/src/managed_agents/backend.rs
Locator: Provider discovery and invocation; docs/remote-agents.md layers and lifecycle
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.
Retrieved: 2026-11-13

## buzz:RUN-02

Finding: 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.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: Not specified

Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-backend-kubernetes/src/pod.rs
Locator: Pod construction, lines 108-175; desktop/src-tauri/tauri.conf.json externalBin
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.
Retrieved: 2026-11-13

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-acp/src/base_prompt.md
Locator: Repository workflow, lines 130-140
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.
Retrieved: 2026-11-13

## buzz:RUN-03

Finding: The ACP harness detects crashed subprocesses and respawns them but does not persist its own state.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:RUN-05

Finding: Buzz documents workflow capacity rejection and expression timeouts. Agent spend limits remain unestablished.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:RUN-06

Finding: Signed events and search supply activity records.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: Executive summary; Relay boundary
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
Retrieved: 2026-11-07

## buzz:RUN-08

Finding: ACP prompts queue per channel; workflows reject work at capacity instead of queueing.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-acp; buzz-workflow
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.
Retrieved: 2026-11-07

## buzz:TEAM-01

Finding: Buzz documents shared channels and threads with presence and membership boundaries.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-acp/README.md#L137-197
Locator: crates/buzz-acp/README.md lines 137-197 (respond-to modes and examples), release tag desktop-v0.5.28 (commit f87c108)
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.
Retrieved: 2026-11-10

## buzz:TEAM-02

Finding: Buzz documents channel roles, authenticated membership and revocation operations. Enterprise SSO remains unknown.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: Executive summary; Relay boundary
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/docs/admin/README.md#L96-127
Locator: docs/admin/README.md lines 96-127 (Principal model, Capabilities by role), release tag desktop-v0.5.28 (commit f87c108)
Finding: Relay staff are resolved to Operator or Moderator roles with a documented capability table; only Operators manage the operator roster.
Retrieved: 2026-11-10

## buzz:TEAM-03

Finding: Workflow approval gates are documented as incomplete and mark affected runs failed.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

## buzz:TEAM-04

Finding: Buzz documents signed persisted events and a hash-chained append-only audit log. Retention guarantees remain unknown.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: Executive summary; Relay boundary
Finding: One relay is authoritative for signed events, authentication, persistence, search and automation. Community host boundaries are explicit.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

## buzz:SHIP-01

Finding: Buzz marks canvases and media as working today.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src/features/projects/ui/ProjectPullRequestFilesChangedPanel.tsx#L656
Locator: desktop/src/features/projects/ui/ProjectPullRequestFilesChangedPanel.tsx line 656 (ProjectPullRequestFilesChangedPanel), release tag desktop-v0.5.28 (commit f87c108)
Finding: The desktop Projects view renders a files-changed diff panel for a pull request, beside create, review and merge controls.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/preview-features.json#L10-14
Locator: preview-features.json lines 10-14 (projects), release tag desktop-v0.5.28 (commit f87c108)
Finding: Projects, the git repository browser and collaboration view, is listed as an opt-in desktop preview feature.
Retrieved: 2026-11-10

## buzz:SHIP-03

Finding: Git event and hosting support is listed as working.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The desktop pull request UI sits in the opt-in Projects preview; pull requests are NIP-34 events on Buzz git hosting, not GitHub.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src-tauri/tauri.conf.json#L55-62
Locator: desktop/src-tauri/tauri.conf.json lines 55-62 (bundle.externalBin), release tag desktop-v0.5.28 (commit f87c108)
Finding: The desktop bundle ships buzz-acp, buzz-agent, buzz-backend-kubernetes and the buzz CLI as sidecar binaries.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-cli/src/lib.rs#L264
Locator: crates/buzz-cli/src/lib.rs line 264 (pr subcommand) and line 1631 (open), release tag desktop-v0.5.28 (commit f87c108)
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.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/desktop/src/features/projects/ui/ProjectPullRequestFilesChangedPanel.tsx#L656
Locator: desktop/src/features/projects/ui/ProjectPullRequestFilesChangedPanel.tsx line 656 (ProjectPullRequestFilesChangedPanel), release tag desktop-v0.5.28 (commit f87c108)
Finding: The desktop Projects view renders a files-changed diff panel for a pull request, beside create, review and merge controls.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/preview-features.json#L10-14
Locator: preview-features.json lines 10-14 (projects), release tag desktop-v0.5.28 (commit f87c108)
Finding: Projects, the git repository browser and collaboration view, is listed as an opt-in desktop preview feature.
Retrieved: 2026-11-10

## buzz:OWN-01

Finding: Buzz repository uses Apache-2.0 for the client and relay source, subject to component notices.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI; Buzz mobile clients
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

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.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/LICENSE
Locator: Root license grant
Finding: The cited root license governs this repository distribution, subject to component notices.
Retrieved: 2026-11-07

## buzz:OWN-02

Finding: Buzz can run a community on an operator-owned relay.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2027-02-05
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

## buzz:OWN-03

Finding: Buzz documents local/operator-owned data stores and signed-key authentication. Telemetry and model training policy remain unknown.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-12-07
Plan: Not specified
Surface: Buzz relay and CLI
Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.

Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/ARCHITECTURE.md
Locator: buzz-auth; buzz-db; buzz-pubsub; buzz-audit; Known limitations
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.
Retrieved: 2026-11-07

## buzz:OWN-04

Finding: 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.

Verification: sourced
Checked: 2026-11-10
Scheduled recheck: 2026-11-24
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: First-party pricing sources read 2026-11-10

Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.

Source: https://github.com/block/buzz/blob/main/README.md
Locator: 'What is this, really?'; 'I want my own hosted relay'
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.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/main/LICENSE
Locator: Apache License 2.0, section 2 (Grant of Copyright License)
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/crates/buzz-acp/README.md#L72-104
Locator: crates/buzz-acp/README.md lines 72-104 (Running with Codex, Running with Claude Code), release tag desktop-v0.5.28 (commit f87c108)
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.
Retrieved: 2026-11-10

## buzz:OWN-06

Finding: README explicitly separates working, unfinished and vision capabilities.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI; Buzz mobile clients
Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.

The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.

Source: https://github.com/block/buzz/blob/96af488d968a1ae9d961c2132bea27822735f8da/README.md
Locator: Overview, setup, features and component boundaries
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.
Retrieved: 2026-11-07

## buzz:OWN-08

Finding: Buzz desktop builds are free downloads from the public GitHub release under Apache-2.0; relay hosting and agent provider costs are separate.

Verification: agent-cross-checked
Checked: 2026-11-10
Scheduled recheck: 2026-11-24
Plan: Not specified
Surface: Buzz desktop workspace; Buzz relay and CLI
Version: Not specified

Hosting costs for a relay and agent provider charges were not checked. No installed-product test was run.

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/README.md#L117-133
Locator: README.md lines 117-133 (I just want to try the app), release tag desktop-v0.5.28 (commit f87c108)
Finding: Packaged macOS, Linux and alpha Windows builds are downloaded from the public GitHub release; the README names no price.
Retrieved: 2026-11-10

Source: https://github.com/block/buzz/blob/f87c10895ea35a9a2cea629fef1d7532a3fecbc5/LICENSE
Locator: LICENSE at commit f87c108; Apache License 2.0, section 2 (Grant of Copyright License)
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Retrieved: 2026-11-10