Continuity v0.2.0
After one-time setup, tested Claude Code and Codex integrations load project context at session start and save eligible lessons and unfinished-work handoffs after edits. Normal provider sessions need no Continuity commands.
- Project-bound MCP detail tools provide context, search and the latest open handoff. A later session can complete and close a handoff without losing its history.
- An optional local runtime keeps source state fresh and serves the Dashboard. Windows can start it at sign-in through a current-user task.
- Source-scope controls, provenance checks and bounded context selection keep retrieval within the registered project and workspace.
- Doctor reports stale or partial provider integrations and gives explicit repair steps. Windows child-process launching uses trusted system executables and constrained environments.
Continuity remains local-first and provider-neutral. Claude Code and Codex are the first-class tested integrations; other clients use the documented CLI, MCP or host API. The core needs no API key, does not mine transcripts, and does not search across projects. The optional runtime and provider integrations require explicit setup.
Install the attached continuity-local-0.2.0.tgz with Node.js 24.13 or newer on the Node 24 line. For an existing v0.1.x home, follow the upgrade guide, including a complete backup and integration status checks. Host API 2 callers must await host.doctor(). Upgrading v0.1.0 state migrates SQLite schema 4 to 5; do not reopen it with v0.1.0.
Security: Windows users of v0.1.0 should upgrade to v0.2.0. See GHSA-x8mx-rp6r-jf6c.