Concord: let Copilot CLI share work-state with Claude Code, Cursor, and other agents

[alexechoi]

I'm building Concord, an open-source MCP server for agents working on the same project. It provides shared presence, file claims, task context, messages, and handoffs across supported coding clients.

Concord has a Copilot CLI integration. A workflow I'd like feedback on: ask Copilot to take the tests while another agent takes implementation, with both recording their intended scope and asking each other questions through Concord.

It also connects separate Copilot CLI sessions. One can handle implementation while another reviews or tests, with a distinct identity for each session and shared context between them.

npm install -g @concord-ai/concord-mcp
cd your-repo
concord setup

Restart existing sessions after setup. For live idle delivery on compatible versions, start Copilot with concord adapters copilot. Plain copilot sessions use hooks and receive queued messages during their next turn; the hosted delivery path requires Copilot CLI 1.0.100 or newer.

Copilot CLI guide.

Concord Cloud connects local, remote, and async agents in one shared workspace. Work can continue across machines and at different times, with task context and handoffs available for the next agent. Try Concord Cloud.

I'd welcome reports on concurrent session identity, overlapping claims, and prompt/reply delivery with another harness. Please include the CLI version and concord adapters doctor result.