Upgrading & Uninstalling

Upgrading

warden --update

This checks the installed version against the latest release, prints where the release lives, asks for confirmation, and applies the update using whichever install method it detects (cargo, npm, or standalone binary). Configuration, session data, and learned patterns are preserved across upgrades.

To skip the confirmation prompt:

warden --update --yes

To check without installing:

warden --update --check

The dashboard also shows an update banner when a newer release is available.

After Upgrading

warden --version

Nothing else is required. The next hook call notices the running server is on the old version and respawns it — the same check that picks up a changed rules.toml.

Version Compatibility

Session data is backward-compatible across minor versions. Rule files are forward-compatible: rules written for older versions continue to work on newer versions.

Uninstalling

warden uninstall

This removes hook registrations, stops the server, and optionally deletes all Warden data (~/.warden/). Your AI assistant will continue to work normally — it just won’t have Warden’s protection.