Updates & uninstall

# Update Rift

If you are on v1.2.0-alpha or later, run the built-in updater. It installs the newest release and keeps your settings.

rift --version
rift update
rift --version

On an older alpha, use the current installer. A version-specific installer is pinned to that release; the updater follows the newest release. Restart an open dashboard or agent after updating so you are using the new binary.

Rift verifies update manifests and archive checksums. If a download or verification fails, read the reported error and retry with a working connection. Do not bypass verification to force a failed download.

The published version documented here is v1.3.1-alpha. Read its release notes for changes and platform support.

# Automatic update checks

Rift checks for a new release at most once a day when you launch the dashboard or run setup. It asks before installing. This is a release check, not telemetry or an upload of project activity.

To disable these automatic checks, set RIFT_NO_UPDATE_CHECK=1 in the environment where you run Rift.

export RIFT_NO_UPDATE_CHECK=1

$env:RIFT_NO_UPDATE_CHECK = "1"

These examples affect the current shell. Use your shell profile if you want the setting in future terminals. You can still run rift update explicitly.

# Preview and uninstall

First inspect the removal plan. The dry run changes nothing.

rift uninstall --dry-run

When ready, remove the managed installation and Rift-owned integrations:

rift uninstall

The uninstaller removes the managed binaries and its PATH entry. Captured history is preserved by default. Agent configuration owned by another tool is not a reason to delete those files yourself; follow any reported conflicts.

# Remove local runtime data

If you also want to remove machine-local caches, settings, and project runtime state, review the purge plan first:

rift uninstall --purge --dry-run

The explicit purge command is rift uninstall --purge --yes. It removes that local data and requires confirmation through --yes. It still preserves captured Git records and repository policy files; it is not a command to erase all history from a repository.

Read privacy & data for the distinction between captured history and local runtime state. If removal reports a problem, keep the output and use the troubleshooting guide.