Update the CLI

Check the installed Ansight CLI release, apply updates, change channels, or recover with the standalone platform updater.

Ansight CLI releases have a human version, a daily YYYYMMDDNN build number, and a public or preview update channel. The installation receipt preserves the selected channel and managed install locations.

The public updater reads https://www.ansight.ai/release.json; preview uses https://www.ansight.ai/preview/release.json. Both feeds identify product: "cli" and publish the CLI version, build number, and archive/checksum URLs.

Check the installed release

Show the current build identity, runtime, executable path, and update channel:

ansight version
ansight version --json

Check the installed channel for a newer build without changing the current installation:

ansight update check

The CLI also checks its installed feed at most once per day during interactive use and prints a non-blocking suggestion when a newer build is available.

Apply an update

Install the newest build from the current channel:

ansight update

The platform installer validates the release archive’s SHA-256 before changing the active CLI. Account, agent-skill, startup, and PATH setup are not repeated.

To inspect or move to another release channel:

ansight update check --channel preview
ansight update --channel preview

Select an exact release by supplying both identity components:

ansight update check --version <version> --build-number <YYYYMMDDNN>
ansight update --version <version> --build-number <YYYYMMDDNN>

Use --json with checks or updates when a script needs structured output. See the version and update command reference for the complete option contract.

Restart an older resident host

Installing a CLI build does not replace the code already loaded by a running host. Commands forwarded to that host continue using its build, even when the new executable’s help lists additional options such as --headless.

Compare the executable and host identities:

ansight version --json
ansight host status --json

When the host is older, finish or coordinate any active runs before restarting it. A restart interrupts live sessions. Use the same data directory and startup options as before; for a manually managed host, stop it and run the new build in its persistent terminal:

ansight host stop
ansight host run

For a service-managed host, use its service manager to restart it. Do not start a second host against the same data directory or restart a shared host without coordinating with its users.

Use the standalone updater

If the installed CLI cannot update itself, use the matching platform updater. On macOS or Linux:

curl -fsSL https://www.ansight.ai/update.sh | bash

On Windows PowerShell:

irm https://www.ansight.ai/update.ps1 | iex

The standalone updater discovers the installation receipt, preserves its channel and install locations, downloads the selected release, and delegates to the checksum-validating installer. It does not rerun account, agent-skill, startup, or PATH setup.

Complete custom feeds keep both their custom manifest and download locations. If a development install instead leaves a canonical Ansight manifest paired with a local file:// package directory, the updater repairs that inconsistent pair by using the channel’s canonical download location.

Check what the standalone updater would select without installing it:

curl -fsSL https://www.ansight.ai/update.sh | bash -s -- --check

For Windows, download the script before passing PowerShell parameters:

$updater = Join-Path $env:TEMP 'ansight-update.ps1'
irm https://www.ansight.ai/update.ps1 -OutFile $updater
& $updater -Check

Run a downloaded update.sh --help or Get-Help .\update.ps1 for standalone channel and exact-build options.