Installation

The Ingrain CLI ships as a single self-contained binary.

Prerequisites

• macOS, Linux, or Windows (x86_64 or arm64; Windows is x86_64 only).
• An install token in INGRAIN_INSTALL_TOKEN, or available to paste when the script prompts. Prebuilt binaries are currently distributed through a gated proxy at cli.ingrainlabs.dev; tokens are shared out of band until public binary releases are available.

Install

The install scripts are served by cli.ingrainlabs.dev. Set your install token, then run the one-liner for your platform.

macOS / Linux

export INGRAIN_INSTALL_TOKEN=<your-token>
curl -fsSL https://cli.ingrainlabs.dev/install.sh | sh

Windows (PowerShell)

$env:INGRAIN_INSTALL_TOKEN = "<your-token>"
irm https://cli.ingrainlabs.dev/install.ps1 | iex

The installer downloads the latest release binary, verifies its SHA-256 sum against the release manifest, and places ingrain on your PATH.

Verify the install

ingrain --help

Prints Usage: ingrain ... and the available subcommands. If it errors instead, see Troubleshooting below.

Upgrade

Once installed, the CLI manages its own upgrades:

ingrain upgrade

This re-fetches the latest release through the same install proxy. See the upgrade command for flags and the [upgrade] config section for customising the proxy URL.

Uninstall

ingrain uninstall

Removes the ingrain binary and its PATH entry. Your ~/.ingrain/ directory is left in place — conf.toml and any session data are preserved so you do not lose your settings if you reinstall. Delete it by hand if you want a clean wipe.

Troubleshooting

• 401 Unauthorized when running the install script — the token in INGRAIN_INSTALL_TOKEN is missing, expired, or malformed. Obtain a fresh one out of band.
• ingrain: command not found after install — the installer wrote the binary to your install dir but the shell hasn’t picked it up. Open a new shell or source your profile.