Install the CLI

One command puts the `crusible` binary on your machine, after it verifies the release signature and the checksum in front of you.

What you'll have

The `crusible` binary in `~/.local/bin`, installed from a release whose signature and checksum were verified first, and answering `crusible --version`. 5 minutes

Prerequisites

A Mac or a Linux machine on amd64 or arm64. The release builds those four and nothing else.
`curl`, which every Mac and most Linux images ship.
`cosign`, which checks the release signature. The installer refuses to run without it; [sigstore's install page](https://docs.sigstore.dev/system_config/installation/) has it for every platform.

Welcome. This is the shortest page in these docs, and it ends with crusible on your machine. One command fetches the release built for your Mac or your Linux machine, and before it writes a single byte it checks two things in front of you: the signature over the release’s checksum file, and your download against that file. You watch both checks pass in your terminal. It never asks you for sudo, and the binary lands in ~/.local/bin, a directory that is yours.

Open github.com/crusiblehq/app/releases and find the newest crusible-v… tag. Other components publish releases on the same page, so use only a crusible-v… tag. The version is the number after crusible-v.
Result You have a version number, such as `0.15.0`.
Run curl -fsSL https://crusible.dev/install.sh | sh -s -- --version <semver> in a terminal, with the version from step 1 in place of <semver>.
Result The script narrates as it goes — “crusible: downloading …”, “crusible: verifying the signature over checksums.txt”, “crusible: verifying …” — and ends with “crusible: installed to …/.local/bin/crusible”, followed by a line beginning “binary_version=” that names the version it installed, and one line on how to move to a newer version.
Run crusible --version.
Result One line, beginning “binary_version=” and naming the same version the script reported.
If this doesn't work
could not download crusible_…tar.gz, followed by Does version … publish a … archive?. The script found no release for that version. Check the number against the tag list from step 1, without the crusible-v prefix, and run step 2 again. Without --version, the script asks for the version pinned inside it, and that release is not published. command not found in step 3. The script told you: note: ~/.local/bin is not on your PATH. Run it by its full path, ~/.local/bin/crusible --version, and add ~/.local/bin to your shell’s PATH so step 3 holds next time. is not writable, and this installer will not use sudo. The directory is not yours to write. Run step 2 again and add a directory that is yours: --dir $HOME/bin. needs cosign. The installer stopped before downloading anything. Install cosign from the address it printed, then run step 2 again. did not verify or does not match. The script installed nothing, and says so: NOTHING was installed. Run step 2 once more to rule out a truncated download. If it fails twice, stop, and follow Verify a download instead: the same install, step by step, with every file in front of you before anything runs. unsupported operating system or unsupported architecture. The release builds macOS and Linux on amd64 and arm64, and there is no build for this machine.

That is it: crusible is yours, and you watched it earn its place — signature checked, checksum checked, then installed, in that order. The script installs one version and does not replace itself, and its last line says so. Planned The plan includes a crusible update command. When a newer version is out, the same command with sh -s -- --version <semver> in place of sh brings it in. Your first melt is a sign-in away.