Concord 0.12
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.
Features
- Normalise repositories to project keys, as Concord Cloud does #153 @alexechoi
- Concord cloud login and logout #154 @alexechoi
- Concord cloud link, unlink and status #155 @alexechoi
- Forward the MCP tools to Concord Cloud in a linked repository #156 @alexechoi
- Bearer tokens from an API key or a refreshed browser login #157 @alexechoi
- Concord cloud login signs in through the browser #159 @alexechoi
- A cloud runtime client for sessions #160 @alexechoi
- Cloud runtime state for sessions: drain tickets, watcher state, hook timeouts #161 @alexechoi
- The cloud inbox: register, drain and watch a session against Concord Cloud #162 @alexechoi
- The inbox commands run against Concord Cloud in a linked repository #163 @alexechoi
- The session-start and edit-guard hooks ask Concord Cloud in a linked repository #164 @alexechoi
- Who, tasks and status read Concord Cloud in a linked repository #165 @alexechoi
- Codex receives messages live from Concord Cloud in a linked repository #169 @alexechoi
Maintenance (1)
- Prepare 0.12.0 release #168 @alexechoi
Install or upgrade Concord.
npm install -g @concord-ai/concord-mcp