concord ai
…

Changelog

What changed in Concord.

Each release of the MCP server and CLI, summarised. The full notes and every pull request live on GitHub.

  1. v0.14.1

    2 releases

    Global mode and project-scoped tasks

    Concord now works in repositories where concord setup was never run. Work there goes to one machine-wide store, and every task carries a project, so a single store can hold several repositories without mixing them. concord setup offers global mode for these repositories, and Cursor joins it through MCP roots and its session hook. When you are signed in, Concord Cloud becomes the default store, with a shared general workspace for work outside any repository.

  2. v0.13.0

    goose support and Windows fixes

    Concord adds an integration for goose, and the CLI can now spawn the concord executable on Windows. The demo run script drops the deprecated --agent-comms flag. Three new contributors shipped their first changes in this release.

  3. v0.12.0

    Concord Cloud

    The first release that talks to Concord Cloud. concord cloud login signs in through the browser or with an API key, and concord cloud link connects a repository. In a linked repository the MCP tools, the inbox commands, who, tasks and status, and the session-start and edit-guard hooks all go to the cloud instead of the local store, so agents on different machines share one workspace. Codex receives messages live from the cloud. Repositories are now identified by a normalised project key, the same way the cloud identifies them.

  4. v0.11.0

    Quieter setup, faster status

    concord setup no longer edits your root .gitignore: the .concord/ directory ignores itself instead. status stops scanning historical tasks and drops an N+1 query in reviews, and relay heartbeats are spread out so many agents don't refresh at the same moment. The MCP SDK moves to 1.31.0.

  5. v0.10.5

    6 releases

    Reliable live messaging

    Live message delivery is reworked to be reliable across harnesses, and Concord now tracks when a receiving agent goes idle and recovers it. Patch releases in this line published Concord to the official MCP Registry, added update notices and upgrade prompts, stored the outcomes agents report when they finish a task, and made overlap checks, status and message drains faster.

  6. v0.9.0

    Archive idle agents instead of dropping them

    Agents that haven't been seen for an hour are now archived rather than removed, so their record survives the end of the session.

  7. v0.8.0

    Identity from the session

    An agent's identity now comes from its harness session instead of being minted fresh, so one session keeps one identity. Tasks track their own activity timestamps, and claim metadata is validated before it is stored.

  8. v0.7.1

    2 releases

    Messaging in plain claude and codex sessions

    Live messaging between agents now works in ordinary claude and codex sessions. The Whack-a-Mole demo runs with real model sessions, and 0.7.1 publishes the relay plugin and installs it from concord setup. Dependencies move to zod 4, commander 15 and ink 7.

  9. v0.6.1

    2 releases

    Five workflow tools

    The MCP surface is consolidated into the five workflow tools Concord uses today: start_work, inspect_work, update_work, transfer_work and finish_work. Underneath, task ownership is versioned and enforced on every write, assignment and handoff get explicit lifecycles with acknowledged delivery, and concord install registers the MCP server. 0.6.1 adds live prompting between agents. Node 22 or later is now required.

  10. v0.5.0

    Anonymous telemetry

    Concord starts collecting anonymous usage telemetry, including which CLI commands are run.

  11. v0.4.1

    2 releases

    Presence and the live dashboard

    Concord learns who is online. A presence registry tracks live agents, links them to their claims and flags work whose owner has gone stale. Claude sessions register themselves, and a terminal dashboard shows the live roster. 0.4.1 adds a notice when an update is available.

  12. v0.3.0

    Task memory

    Tasks get their own memory: tools for recording what an agent learned while working, stored with the task instead of in the session. concord init also stops the Concord workspace from being committed.

  13. v0.2.0

    Overlap checks at edit time

    Overlap detection gets sharper and moves closer to the edit. Labels match on normalised words rather than exact strings, oversized claims get a nudge to split, and concord check plus an opt-in Claude Code PreToolUse hook can stop an edit to a claimed file. Work-state changes are pushed through MCP resource updates and concord watch, and tasks can have parent and child ids.

  14. v0.1.1

    First release

    The first published version: an MCP server with overlap detection on claim_work, handoffs and review-ready packets, backed by SQLite, plus the concord CLI with init, status, tasks, handoff, doctor and install. Published to npm as @concord-ai/concord-mcp.