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.

When Wenlan offers an update, follow the prompt to install it. You can also open About Wenlan and choose Check for updates. If you install the macOS app manually, replace the old app with the new one and open it; quit Wenlan 0.17.0 or older first.

On macOS Apple Silicon with Node.js, run the installer with --version to check and refresh the runtime without rerunning setup. If it cannot check for a newer release, it can reuse the installed runtime and reports that; compare the printed version with the release you intend to install. Restart the daemon, then check status and doctor. Other platforms use their supported installation path.

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

Run /wenlan to check whether Claude Code can reach Wenlan. If it cannot connect, follow its setup prompts.

If wenlan-mcp moved, or a client still launches an old path, rerun wenlan connect 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 Wenlan doctor or a small capture/recall round trip.

In the desktop app, turn off Run Wenlan in background at login in Settings, quit the app, then remove the app or run the Windows uninstaller. Your knowledge folders remain.

For a CLI installation, wenlan background off stops the daemon and disables autostart; it does not remove the service registration. Remove any Wenlan entries you added to client settings separately. For remaining files and credentials, consult the removal details.

Uninstalling the app or stopping the background service does not delete your library. Before deleting knowledge folders, decide whether you need them and make a backup. They can contain private captures, pages, and session notes.