Concord 0.14
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.
Fixes
- Keep a user's own concord server during the Cursor migration #194 @wysRocket
- Warn on overlap with assigned, blocked and handed-off tasks #185 @vishalhabib99
- Global mode follow-ups: concord watch, Grok TOML, early tool calls #191 @alexechoi
- Doctor detects and repairs dangling harness adapter links #203 @alexechoi
Other changes
- Drop the 600 LOC PR limit from CLAUDE.md #199 @alexechoi
Maintenance (4)
First contributions from @wysRocket, @vishalhabib99.
Features
- Scope tasks to a project so one store can hold several repositories #181 @alexechoi
- Route repositories that were never set up to a machine-wide store #182 @alexechoi
- Concord setup offers global mode for repositories that were not set up #183 @alexechoi
- Cursor joins global mode through MCP roots and its session hook #184 @alexechoi
- Signed in, Concord Cloud is the default — with general for work outside a repository #198 @alexechoi
Fixes
- Treat Ctrl+D at a setup prompt as no answer #192 @alexechoi
Maintenance (1)
- Prepare 0.14.0 release #193 @alexechoi
Install or upgrade Concord.
npm install -g @concord-ai/concord-mcp