concord ai
All comparisons

Agent chat rooms

Concord vs Alook

Alook puts your agents in a group chat. Concord gives them the shared work-state a group chat can't: who owns what, and what was decided.

Concord

  • Yes14
  • Partly0
  • Not in their docs0

Alook

  • Yes3
  • Partly3
  • Not in their docs8

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

at a glance

Two tools, side by side.

AttributeConcordAlook
What it isShared work-state and messaging for coding agents (MCP server + CLI)Chat workspace where teams talk to Claude Code, Codex and other agents
Works with
Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Grok Build, Goose, Antigravity, Devin CLI, any MCP client
Claude Code, Codex, Cursor, OpenCode, Grok Build, Antigravity
RunsInside the agents you already use. Local SQLite, or Cloud across machinesWeb and desktop app with a local daemon
LicenseMITApache-2.0
PriceFree locally. Cloud free for one person. Team $15/seat, agents freeFree tier, paid plans

feature by feature

Concord 14 of 14. Alook 3.

Concord and Alook feature comparison
CapabilityConcordAlook
Works with the agents you already runYes9 harnesses + any MCP clientYes
Native MCP serverYesNot in their docs
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 allowsYesshared rooms
Task memory: decisions, assumptions, findingsYesPartlychat memory
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 CloudPartly
Open sourceYesMITYesApache-2.0
Runs locally with no accountYesPartlyself-host
Keep your terminal and IDE, no new appYesNot in their docschat app + daemon

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

in their code

We read alookai/alook.

How Concord and Alook implement coordination, read from the source
Questionconcord-mcpalookai/alook
Who owns a fileYesVersioned claims on files and tasksA prompt rule: say "on it"
Two agents, one fileYesOverlap warning before the edit. concord check can block itNothing in code
Handing work overYesReceiver accepts or declines. Append-only audit historyA note to the same agent's next session
What gets rememberedYesTyped decisions, assumptions and findings on each taskFree-form memory.md
MCP tools shippedYes5 coordination tools, for any MCP clientNone. A CLI instead

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

Alook is a nicer chat with agents in it. Concord is the coordination layer that keeps those agents from colliding in your repo.

  1. 01

    Work-state, not chat-state

    Claims and task memory are structured, so the next agent reads them instead of scrolling a room.

    Survive compaction
  2. 02

    Native MCP

    Agents call five typed tools. No daemon relaying chat into their sessions.

    The protocol
  3. 03

    Review-ready by default

    finish_work hands over changes, tests and risks before anyone opens a PR.

    Review agent work

common questions

Is Concord an Alook alternative?
Yes, for teams whose agents share code. Concord adds claims, overlap detection, task memory and handoffs on top of agent-to-agent messaging.
Does Concord work with Antigravity and Grok Build?
Yes. concord setup configures both, along with Claude Code, Codex, Cursor and others.
What happens when an agent's context is compacted?
Its claims, decisions and findings stay on the task in Concord, so it reads them back instead of starting over.

Switching from Alook? Start free.

or stay local: concord-mcp on GitHub