The CLI can identify whether the current executable is owned by the native
installer or a supported package manager and update through that same path.
Check without installing
--check reports whether an update is available without changing the
installation.
Install the latest release
For a native installation on macOS, Linux, or Windows, Clawdi downloads the
exact release artifact, verifies its manifest checksum, and switches the
stable launcher to the new version. For an npm-owned installation, it uses
npm to install the exact version selected by the update check.
Native installations on CLI 0.15.8 or earlier cannot update themselves.
Run the native installer from Install the Clawdi CLI once;
later versions update normally. npm installations are unaffected.
If Clawdi cannot identify the installation owner, it does not overwrite an
unknown executable. Follow the exact manual command printed by the CLI, or
reinstall through the path shown on Install the Clawdi
CLI.
Control background updates
Background update checks are enabled by default in the released CLI.
Automatic updates install a release only after this computer has seen it as
the latest version for at least 24 hours, and skip intermediate releases.
clawdi update installs the latest release right away. To opt out of
automatic updates while keeping manual clawdi update available:
Restore the default behavior:
For one process, set CLAWDI_NO_AUTO_UPDATE=1 instead of changing stored
configuration.
Use an exact version
To move to a specific published release, install that exact version through
the same method you chose originally:
macOS and Linux
Windows
npm
X.Y.Z with a published semantic version, then run clawdi --version.
The built-in --help output is the command reference for the installed
version. Last modified on October 6, 2026
