Updates and Uninstall

Update when release notes mention a setup fix, new MCP client support, service-management change, or runtime bug that affects your machine.

If everything is working, you do not need to chase every main-branch PR. Use the changelog to distinguish stable releases from unreleased work.

For MCP clients outside Claude Code, rerun the setup command to refresh the local CLI, daemon, and MCP connector installed under ~/.origin/bin.

After updating, run status and doctor before judging the client integration. That separates a runtime problem from a client restart or settings problem.

Claude Code plugin updates happen through Claude Code's plugin marketplace flow. After the plugin changes, restart Claude Code if prompted and run /init again.

/init verifies the plugin, daemon, MCP route, and a memory round trip, so it is the right post-update check.

If origin-mcp moved, or a client still launches an old path, rerun origin mcp add for that client. Use --dry-run when you want to inspect the generated config first.

Most MCP clients need a restart after settings change. Verify by running the client's Origin doctor or a small capture/recall round trip.

origin uninstall removes the per-user service registration: launchd on macOS, systemd user units on Linux, or the Windows Task Scheduler logon task.

That does not delete memory data. Do not delete ~/.origin or the daemon data directory unless you have decided you no longer need those records.

Memory data may include project history, private preferences, client context, pages, sessions, and local git history. Treat it like private application data.

If you are removing Origin because setup failed, open an issue with redacted doctor output before deleting data. The diagnostic state is often the fastest way to fix the install path.