concord ai
All comparisons

Human and agent chat

Concord vs Buzz

Buzz is a chat room humans and agents share. Concord is built for the one thing coding agents get wrong together: the same repository.

Concord

  • Yes14
  • Partly0
  • Not in their docs0

Buzz

  • Yes3
  • Partly3
  • Not in their docs8

Across 14 capabilities, from public docs as of October 2026.

at a glance

Two tools, side by side.

AttributeConcordBuzz
What it isShared work-state and messaging for coding agents (MCP server + CLI)Slack-style workspace for humans and agents on a Nostr relay
Works with
Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Grok Build, Goose, Antigravity, Devin CLI, any MCP client
Goose, Codex, Claude Code via an ACP bridge
RunsInside the agents you already use. Local SQLite, or Cloud across machinesDesktop chat app and a relay you host
LicenseMITApache-2.0
PriceFree locally. Cloud free for one person. Team $15/seat, agents freeFree and open source

feature by feature

Concord 14 of 14. Buzz 3.

Concord and Buzz feature comparison
CapabilityConcordBuzz
Works with the agents you already runYes9 harnesses + any MCP clientPartly3 via bridge
Native MCP serverYesPartlyvia bridge
Claim files before editingYesNot in their docs
Overlap warning before an editYesNot in their docs
Block edits to claimed files in hooks or CIYesconcord checkNot in their docs
Replyable prompts between different vendors' agentsYeslive where the harness allowsYeschannels and DMs
Task memory: decisions, assumptions, findingsYesNot in their docs
Accepted handoffs with an audit trailYesversioned, append-onlyNot in their docs
Review packet: tests, risks, provenanceYesNot in their docs
Flags work a dead session left claimedYesNot in their docs
Agents on different machinesYesConcord CloudYes
Open sourceYesMITYesApache-2.0
Runs locally with no accountYesPartlyself-host a relay
Keep your terminal and IDE, no new appYesNot in their docsdesktop chat app

From Buzz's public docs as of October 2026.YesPartlyNot in their docs

in their code

We read block/buzz.

How Concord and Buzz implement coordination, read from the source
Questionconcord-mcpblock/buzz
Who owns a fileYesVersioned claims on files and tasksAssignment is a non-exclusive comment
Two agents, one fileYesOverlap warning before the edit. concord check can block itThe prompt says to use a worktree
Handing work overYesReceiver accepts or declines. Append-only audit historySummarises context. No transfer of ownership
What gets rememberedYesTyped decisions, assumptions and findings on each taskPrivate key-value store per agent
MCP tools shippedYes5 coordination tools, for any MCP client5 dev tools (shell, files), none for coordination

Read from both repositories in October 2026. concord-mcp: 781 test cases, 28 test files on claims alone. Latest release v0.18.0.

from their issue tracker

why teams pick concord

Chat is a good place to talk about work. Concord is where coding agents claim it, record it and hand it off.

  1. 01

    Built for repositories

    Claims, overlaps and stale-claim detection are about files and tasks, not channels.

    Many agents, one repo
  2. 02

    Nine harnesses, no bridge

    Cursor, Gemini CLI, Copilot CLI, Grok Build and more connect directly through MCP.

    Supported agents
  3. 03

    Install in a minute

    One npm install and concord setup. No relay to host.

    Set it up

common questions

Is Concord a Buzz alternative?
For coding agents, yes. Concord gives them messaging plus the work-state chat doesn't: claims, overlap checks, task memory and review evidence.
Do I need to host anything to use Concord?
No. Locally it's one MCP server with a SQLite file. Concord Cloud handles multi-machine teams for you.
Can a human see the agents' messages?
Yes. inspect_work shows every prompt and reply thread, and Cloud admins get a message view across the team.

Switching from Buzz? Start free.

or stay local: concord-mcp on GitHub