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

# Install the CLI

> Install the continuous command with Homebrew, a release archive, or the installer script.

`continuous` calls the Continuous Simulation API from your terminal. This guide and the generated reference use v0.1.18. It runs on macOS, Linux, and Windows on x86\_64 and arm64.

<Tabs>
  <Tab title="Homebrew">
    Works on macOS and Linux.

    ```bash theme={null}
    brew install continuous-labs-ai/tap/continuous
    continuous version
    ```

    The formula installs the binary. Run `brew upgrade continuous-labs-ai/tap/continuous` for later releases.
  </Tab>

  <Tab title="Release archive">
    Releases after 0.1.1 ship `checksums.txt` and `checksums.txt.sig`, a detached signature made with the project's GPG key; earlier releases have no signature. The signature proves that the manifest came from the project, and the checksum proves that the archive matches the manifest. These steps need `gpg`; on macOS, install it with `brew install gnupg`.

    First import the signing key. It is [`release-signing-key.asc`](https://github.com/continuous-labs-ai/cli/blob/main/release-signing-key.asc) in the CLI repository, with fingerprint `3F97 24EA E595 A2F9 F3E8 EDA1 AF88 CF5D 4448 F191`. Check that the printed fingerprint matches before you import.

    ```bash theme={null}
    curl -fsSL https://raw.githubusercontent.com/continuous-labs-ai/cli/main/release-signing-key.asc \
      -o release-signing-key.asc
    gpg --show-keys --with-fingerprint release-signing-key.asc
    gpg --import release-signing-key.asc
    ```

    Then download and verify the archive for your platform from the [v0.1.18 release](https://github.com/continuous-labs-ai/cli/releases/tag/v0.1.18). On Linux or macOS:

    ```bash theme={null}
    set -euo pipefail
    version=v0.1.18
    platform=$(uname -s)            # Linux or Darwin
    architecture=$(uname -m)        # x86_64 or arm64
    if [ "$architecture" = aarch64 ]; then
      architecture=arm64
    fi
    archive="continuous_${platform}_${architecture}.tar.gz"
    release_url="https://github.com/continuous-labs-ai/cli/releases/download/$version"
    cd "$(mktemp -d)"
    curl -fsSL "$release_url/checksums.txt" -o checksums.txt
    curl -fsSL "$release_url/checksums.txt.sig" -o checksums.txt.sig
    gpg --verify checksums.txt.sig checksums.txt
    curl -fsSL "$release_url/$archive" -o "$archive"
    grep " $archive\$" checksums.txt | sha256sum -c -
    tar -xzf "$archive"
    mkdir -p "$HOME/.local/bin"
    install -m 755 continuous "$HOME/.local/bin/continuous"
    ```

    `gpg --verify` reports `Good signature from "Continuous CLI Release"`; its warning that the key is not certified means only that you have not signed the key yourself.

    Add `$HOME/.local/bin` to your `PATH`. On macOS use `shasum -a 256 -c -` in place of `sha256sum -c -`.

    On Windows, download `continuous_Windows_x86_64.zip` or `continuous_Windows_arm64.zip`, compare `Get-FileHash` against `checksums.txt`, extract the files to a folder, and add that folder to your user `PATH`.

    Each archive contains the binary, `README.md`, and `LICENSE`.
  </Tab>

  <Tab title="Installer script">
    The installer verifies the archive against `checksums.txt` before it extracts anything.

    ```bash theme={null}
    curl -fsSL https://raw.githubusercontent.com/continuous-labs-ai/cli/main/scripts/install.sh \
      -o install.sh
    CONTINUOUS_VERSION=v0.1.18 \
      CONTINUOUS_INSTALL_DIR="$HOME/.local/bin" bash install.sh
    ```

    Omit `CONTINUOUS_VERSION` to install the latest published release. Omit `CONTINUOUS_INSTALL_DIR` to install to `/usr/local/bin`, or to `~/.local/bin` when `/usr/local/bin` is not writable.

    On Windows, download `scripts/install.ps1` from the same location and run it in PowerShell. It reads the same `$env:CONTINUOUS_VERSION` and `$env:CONTINUOUS_INSTALL_DIR` variables, installs to `$env:LOCALAPPDATA\Programs\continuous` by default, and adds that directory to your user `PATH`.
  </Tab>
</Tabs>

<Note>Only the release archive steps for Linux and macOS verify the signature. Homebrew, the Windows archive steps, and the installer scripts check the archive checksum but not the signature.</Note>

Check the install:

```bash theme={null}
continuous version
```

Confirm that the printed version matches the release you installed.

## Shell completion

Run `continuous completion bash --help` (or `zsh`, `fish`, `powershell`) and follow the printed steps.

## Next step

[Authenticate the CLI](/cli/authentication).