Concord 0.8
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.
Fixes
- Derive agent identity from the session instead of minting one #106 @alexechoi
Other changes
Maintenance (1)
- Bump pnpm/action-setup from 5 to 6 #103 @dependabot[bot]
Install or upgrade Concord.
npm install -g @concord-ai/concord-mcp