Download and install the CLI

The qibdo CLI is distributed as a single binary for use from a terminal or a script. This page is the hand-authored home for installing it. The CLI overview explains the command shape and points to the concepts that apply across the command surface; the command reference is generated from the CLI project’s own command tree.

Prerequisites

You need only a terminal and network access. You do not need a qibdo Cloud account, credentials, Go, or another development toolchain to download and install the binary.

Supported platforms

The installer supports Linux on x86-64 and ARM64, and macOS on Intel and Apple silicon. Windows is not supported yet; the installer reports that explicitly rather than failing with an ambiguous platform error.

Linux amd64 · arm64 Supported macOS Intel · Apple silicon Supported

Windows Not supported yet Coming soon

Install the latest release

Install the current release, when available, with one command:

curl -fsSL https://storage.googleapis.com/qibdo-releases/cli/install.sh | sh

The installer detects the operating system and architecture, downloads the matching archive over HTTPS, and verifies its SHA-256 checksum before installation. It does not require sudo.

Pin a version

Set QIBDO_VERSION to install a published version instead of the current one. Replace vX.Y.Z with the version you want:

curl -fsSL https://storage.googleapis.com/qibdo-releases/cli/install.sh | QIBDO_VERSION=vX.Y.Z sh

Choose an installation directory

Set QIBDO_INSTALL_DIR when the default destination is not suitable or when you want the binary in a user-owned directory:

curl -fsSL https://storage.googleapis.com/qibdo-releases/cli/install.sh | QIBDO_INSTALL_DIR="$HOME/bin" sh

Upgrade

Re-run the latest-release command to upgrade. The installer verifies the downloaded archive before replacing an existing qibdo binary.

Current release

Loading current release details…

Verify a release manually

The installer verifies the archive’s checksum before installing it. Each release also publishes a keyless signature and certificate for checksums.txt; the installer does not verify that signature yet. Manual publisher-signature verification requires Cosign.

To verify an archive yourself, replace vX.Y.Z with a published version and set ARTIFACT to a filename from the current-release table. The example selects Linux amd64; use darwin for macOS or arm64 for an ARM64 system.

VERSION=vX.Y.Z
ARTIFACT=qibdo_${VERSION}_linux_amd64.tar.gz
BASE=https://storage.googleapis.com/qibdo-releases/cli/releases/$VERSION

curl -fsSLO "$BASE/$ARTIFACT"
curl -fsSLO "$BASE/checksums.txt"
curl -fsSLO "$BASE/checksums.txt.sig"
curl -fsSLO "$BASE/checksums.txt.pem"

cosign verify-blob checksums.txt \
  --signature checksums.txt.sig \
  --certificate checksums.txt.pem \
  --certificate-identity "https://github.com/qibdo/qibdo-cloud-cli/.github/workflows/release.yml@refs/tags/$VERSION" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com"

EXPECTED=$(awk -v artifact="$ARTIFACT" '$2 == artifact { print $1 }' checksums.txt)
if [ -z "$EXPECTED" ]; then
  printf 'No checksum found for %s\n' "$ARTIFACT" >&2
  exit 1
fi

if command -v sha256sum >/dev/null 2>&1; then
  printf '%s  %s\n' "$EXPECTED" "$ARTIFACT" | sha256sum -c -
else
  printf '%s  %s\n' "$EXPECTED" "$ARTIFACT" | shasum -a 256 -c -
fi

Without --certificate-identity and --certificate-oidc-issuer, cosign can accept a valid signature from an unrelated identity. The final command verifies that the downloaded archive is the artifact bound by that signed checksum file. After installation, confirm that the binary is available:

qibdo version

Continue with the CLI

• CLI overview for the command shape and the main entry points
• Profiles and configuration for endpoints and organisation context
• Output and scripting for pipelines and non-interactive use
• Command reference for every generated command and flag