> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Update the Clawdi CLI

> Check for Clawdi CLI releases, update through the current installation owner, and verify the result.

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

```bash theme={null}
clawdi --version
clawdi update --check
```

`--check` reports whether an update is available without changing the
installation.

## Install the latest release

```bash theme={null}
clawdi update
clawdi --version
clawdi doctor
```

For a native installation, 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.

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](/installation).

## Control background updates

Background update checks are enabled by default in the released CLI. To opt
out while keeping manual `clawdi update` available:

```bash theme={null}
clawdi config set autoUpdate false
```

Restore the default behavior:

```bash theme={null}
clawdi config unset autoUpdate
```

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:

<Tabs>
  <Tab title="Native">
    ```bash theme={null}
    CLAWDI_VERSION="X.Y.Z"
    curl -fsSL https://clawdi.ai/install.sh | \
      CLAWDI_VERSION="$CLAWDI_VERSION" sh
    ```
  </Tab>

  <Tab title="npm">
    ```bash theme={null}
    npm i -g clawdi@X.Y.Z
    ```
  </Tab>
</Tabs>

Replace `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.