Getting started
concord is a command-line tool that lets several coding agents edit the same repository at the same time and still land code that works together.
Install
concord is a Rust crate with jj built in, so there is no separate jj install. From a checkout of the source:
cargo install --path .
This installs two binaries, concord and git-concord. git runs any git-<name> on your PATH as git <name>, so every command also works as git concord <command>.
The landing gate resolves conflicts with Mergiraf, which needs to be on your PATH (brew install mergiraf). Building needs Rust 1.97.1 or newer.
Teach your agents the protocol
The repository ships an agent skill at skills/concord/. Copy that folder into ~/.claude/skills/ so Claude Code agents know the worker protocol. Copy it again after editing it.
Tell sessions that do not know yet
Add concord as a Claude Code PreToolUse hook on Edit|Write|MultiEdit|NotebookEdit:
"$HOME/.cargo/bin/concord" hook claude
When a session edits the main folder of a project whose board has agents, it gets one note per session saying who is working and how to join with concord plan. The hook never blocks an edit and stays silent everywhere else.
Run agents with no setup
Give each agent its task and tell it to follow the concord skill. Each agent's first command, run anywhere in the project, joins it:
$ concord plan total item_count JOINED agent-1 WORKSPACE agent-1 /work/shop-agent-1 PLANNED agent-1 modifies=['total'] uses=['item_count'] -> from now on work in /work/shop-agent-1: claim, edit, done, finish there
The agent moves into the workspace it was given and does everything else there. Its workspace is a separate copy of the project, starting at your last commit. Uncommitted work in your folder never reaches the agents, so commit what they should build on.
When the last agent of the round finishes cleanly, concord runs the landing gate in the background with your project's tests: a Makefile test target, cargo test, go test ./..., the test script in package.json, or pytest. The result appears in concord log as LANDED or GATE FAIL.
Or set the team up yourself
An orchestrator can create the workspaces up front and run the gate itself:
$ concord init agent-a agent-b agent-c INIT agent-a agent-b agent-c WORKSPACE agent-a /work/shop-agent-a WORKSPACE agent-b /work/shop-agent-b WORKSPACE agent-c /work/shop-agent-c
Dispatch one agent per workspace. Each brief holds the agent's name, its workspace path, its task, and "follow the concord skill (worker protocol)". Do not tell agents about each other's tasks; the board does that.
While they work, concord status shows who holds and waits on which function and who has finished. concord log shows the events. When every agent has reported FINISHED:
concord gate -- cargo test