Installation

Install, check, update, or uninstall Clarvis v0.1.1.

The portable download includes everything Clarvis needs to run, including Bun and the native terminal dependencies. You do not need to install Bun, Node.js, a compiler, or a package manager. No administrator access or source-code checkout is required.

v0.1.1 is an official public 0.x release. Interfaces and stored formats may still change before 1.0, and its binaries are not yet code-signed or notarized.

The commands on this page describe the immutable v0.1.1 release. Keep the checksum, archive, and installer on that same versioned release URL.

Current release

Clarvis v0.1.1 is published from the binary-only public getclarvis/clarvis-releases repository. The release contains the six portable archives, versioned POSIX and PowerShell installers, SHA256SUMS, and the applicable license notices.

Supported release targets

Operating system	Architectures	Archive target	Automated checks
Linux (glibc)	x64, arm64	linux-x64, linux-arm64	Package, installation, and first terminal screen
macOS	Intel, Apple silicon	darwin-x64, darwin-arm64	Package, installation, and first terminal screen
Windows	x64, arm64	windows-x64, windows-arm64	Package, installation, and basic CLI commands

Release checks cover packaging and installation on all six targets, plus a final check that the public packages contain no source maps. On Linux and macOS, they also check the first screen in a pseudoterminal (PTY). On Windows, they check the package manifest, --version, --help, installation, and reinstallation. These automated checks do not replace opening the Windows interface manually or checking SmartScreen warnings. To run without the interactive interface, use clarvis -p.

Linux and macOS

Prerequisites are tar, mktemp, curl, and either sha256sum or shasum. The Linux archives target GNU/glibc systems; Alpine and other musl-only distributions are not supported by these portable assets.

Install the published version with:

curl -fsSL https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.sh | sh

To inspect the installer before executing it, download the installer from the same release, review it locally, and then run it:

curl -fL https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.sh -o install.sh
vi ./install.sh
sh ./install.sh

The default managed installation lives beneath ${XDG_DATA_HOME:-$HOME/.local/share}/clarvis. A small launcher is placed in ${CLARVIS_BIN_DIR:-${XDG_BIN_HOME:-$HOME/.local/bin}}/clarvis. The installer does not edit shell profiles; if the resolved launcher directory is absent from PATH, it prints the line appropriate for adding it and a new shell may be required.

Windows PowerShell

Windows requires PowerShell with Invoke-RestMethod (irm), Invoke-Expression (iex), Invoke-WebRequest, Get-FileHash, and the system tar.exe.

Install the published version with:

irm "https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.ps1" | iex

To inspect the installer first, download and review the same immutable release asset:

Invoke-WebRequest -Uri "https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.ps1" -OutFile ".\install.ps1"
notepad .\install.ps1
& .\install.ps1

The managed installation defaults to %LOCALAPPDATA%\Clarvis. Its bin directory is added to the user PATH unless CLARVIS_SKIP_PATH=1 is set. Reopen the terminal if clarvis is not immediately found.

What the installer verifies

For the detected operating system and architecture, the installer:

1. downloads the target's versioned .tar.gz archive and SHA256SUMS from the same release;
2. requires one exact checksum entry and verifies the downloaded bytes;
3. extracts to a private staging directory;
4. verifies that the staged CLI reports the requested version;
5. refuses to replace an unrelated command or a POSIX launcher owned by another install root;
6. activates the new version only after those checks succeed.

The installer prints the selected version, detected target, resolved destinations, and a numbered status line before each download, checksum, extraction, staged CLI smoke, and activation phase.

Each archive also has an internal release.json manifest with the exact path, size, and SHA-256 of every payload file. Clarvis verifies that manifest again before an update is activated.

To verify the downloaded archive manually, download both the archive and SHA256SUMS, isolate the line whose filename exactly matches the archive, and use the platform's SHA-256 tool. Do not install an asset when its name or digest differs.

Run and update

clarvis --version
cd /path/to/project
clarvis
clarvis --update

The updater works only for a managed portable installation. It does not run automatically on startup. It stages and verifies the candidate, retains the previous version, and changes the active version last. Source checkouts and bun link installations intentionally refuse self-update; update those through Git and the development setup instead.

A prerelease can advance to a newer prerelease or the later stable release. A stable installation does not select prereleases.

Unsigned binaries

The v0.1.1 binaries are not code-signed or notarized. macOS Gatekeeper or Windows SmartScreen may ask the user to confirm a downloaded application. Read the platform warning, confirm the release URL and SHA-256, and follow the operating system's normal approval UI. The Clarvis installers do not disable or bypass platform protections.

Remove Clarvis

The public v0.1.1 installers have an explicit guarded uninstall mode. Download the installer from the same immutable release before running the removal command.

Linux or macOS:

curl -fL https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.sh -o install.sh
sh ./install.sh --uninstall

Windows PowerShell:

Invoke-WebRequest -Uri "https://github.com/getclarvis/clarvis-releases/releases/download/v0.1.1/install.ps1" -OutFile ".\install.ps1"
& .\install.ps1 -Uninstall

The uninstaller shows what it will remove and checks that the files belong to the selected Clarvis installation. It uses the same exclusive lock as installation and updates, and refuses unrelated installations or files that are changing at the same time. On POSIX, the launcher must point to the selected installation folder.

It removes managed versions, current, the installation marker, and the matching launcher. On Windows, it also removes the managed bin entry from your user PATH, even if the launcher is already missing. Set CLARVIS_SKIP_PATH=1 to leave PATH unchanged.

Linked managed directories and non-file marker or activation targets are refused. Cancelling releases the lock before exiting. Unknown files and unrelated launchers are kept and reported. Running uninstall again succeeds without changes, even if those preserved files remain.

User configuration and credentials default to ~/.clarvis (or %USERPROFILE%\.clarvis) and are separate from the managed binary. Removal of the application does not delete that state. Delete it only after backing up anything needed and confirming that stored provider credentials and sessions are no longer required.

If installation paths were overridden, pass the same CLARVIS_INSTALL_ROOT and, on POSIX, CLARVIS_BIN_DIR values to the versioned public uninstaller. The variables are documented in the published install.sh and install.ps1 files.