Upgrade Notes

Origin moves quickly, so distinguish released packages from main-branch work. The changelog and GitHub Releases describe what is shipped; merged PRs can describe work that is not in your installed package yet.

If a doc says an experiment is on main or opt-in, do not treat it as part of the stable runtime until a release page or changelog entry says so.

For MCP clients outside Claude Code, rerun the setup package. That refreshes the local runtime installed under ~/.origin/bin, including the CLI, daemon, and MCP connector.

After setup, run status and doctor before judging a client. A healthy daemon with a broken client usually means MCP settings or restart state, not a failed upgrade.

Claude Code users should update through the plugin marketplace flow, restart Claude Code if prompted, then run /init.

/init is the post-upgrade smoke test because it checks plugin installation, daemon reachability, MCP wiring, and the memory round trip from the tool where you work.

The current public docs describe the v0.7-era runtime shape: Claude Code plugin, npm setup, origin-mcp connector, daemon-first architecture, explicit spaces, local git history, source-backed pages, and cross-platform service registration.

The biggest practical upgrade checks are platform support, package path alignment, and spaces. Confirm your machine's service manager, confirm MCP clients launch the connector under ~/.origin/bin, and confirm the active space is the one you expect.

Most MCP clients read server configuration at startup. If tools disappear after an upgrade, restart MCP clients before rewriting configuration.

If restart does not fix it, rerun origin mcp add for that client. Use --dry-run first when you want to inspect the generated command and path.

Normal upgrades should not delete memory data. origin uninstall removes service registration, not ~/.origin or the daemon database.

For machine migration, manual cleanup, or risky experiments, back up both readable ~/.origin artifacts and the platform daemon data directory. Then verify with doctor and a capture/recall round trip before trusting the restored install.