Where Buzz sits in the tool landscape
Buzz, agent harnesses and single-user agent tools occupy different layers rather than competing for the same job.
Buzz is the team layer: humans and agents in shared rooms with accumulated context and an audit trail. Harnesses — Goose, Claude Code, Codex — are the execution layer, and they run underneath Buzz rather than instead of it. Single-user tools sit alongside for solo work that nobody else needs to see.
The plausible end state is complementary use, with the boundary drawn at whether the work is collaborative.
Why it matters to you
Framing this as a choice wastes effort and produces a wrong answer in both directions. Teams evaluating Buzz often ask "should we switch from X" when the plain answer is that X probably runs inside it.
The boundary also has a cost attached: Buzz adds relay round-trips, so work that gains nothing from being shared pays latency for nothing. See Why is Buzz slower than my harness?
How to apply it
Ask one question: does anyone else need to see, contribute to or audit this work? If yes, Buzz. If no, run the harness directly.
Use the same harness in both places, so moving work between them costs nothing.
If the solo tool is Berd — Block's own desktop workspace, and the sibling product to Buzz — the boundary is sharper and has consequences for client material worth knowing. See Buzz or Berd.
Move work into Buzz at the point it becomes collaborative — when a colleague or specialist needs to see it, when someone joins, when a record matters — rather than at the start out of tidiness.
Explain the layering when recommending Buzz to a colleague who already uses a harness daily; otherwise the latency reads as the product being worse.
If you ignore this
Getting the boundary right means solo iteration stays fast and collaborative work accumulates context. Getting it wrong in either direction is quietly costly: everything in Buzz makes solo work slower, and everything outside it means the shared context that justifies the tool never builds.
Examples
A workshop and a meeting room. You do not do the fabrication in the meeting room, and you do not present in the workshop.
You draft a script directly in your harness in twenty minutes, then bring the result and the reasoning into the project channel where the wider team will discuss it.
Migrating all personal work into Buzz for consistency, then concluding the tool is slow. It is slow at the thing it was not for.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026