Installation

Labcoat publishes CLI executables for macOS and Linux on arm64 and x86_64. Windows is not supported. The Labcoat Network runtime currently supports macOS arm64 and Linux x86_64.

Inspect and install

Review the installer before executing it when your environment requires it:

curl -fsSL https://labcoat.sh/install -o /tmp/install-labcoat.sh
less /tmp/install-labcoat.sh
sh /tmp/install-labcoat.sh

For a direct install:

curl -fsSL https://labcoat.sh/install | sh

The installer selects the latest cli-v* release, requires sha256sum or shasum, verifies the published SHA-256 checksum, and writes labcoat to ${LABCOAT_INSTALL_DIR:-$HOME/.local/bin}. It exits without replacing the current executable if downloading or verification fails.

CLI and runtime versions

Each CLI release owns one exact runtime bundle. On the first labcoat up, Labcoat downloads runtime-manifest.json and its Qubitcoin/WASM assets from the same cli-vX.Y.Z GitHub release:

• macOS: ~/Library/Application Support/Labcoat/runtimes/cli-vX.Y.Z/
• Linux: ${XDG_DATA_HOME:-$HOME/.local/share}/labcoat/runtimes/cli-vX.Y.Z/

After the bundle is present and valid, normal commands use the local cache and do not check GitHub for a newer runtime. Upgrade the CLI to receive a newer runtime. Previous version directories remain available for rollback and are never removed automatically.

Run labcoat binaries --verbose to inspect the active version and paths. Passing --no-download to labcoat up requires the complete matching bundle to already exist.

Install a specific version

curl -fsSL https://labcoat.sh/install | sh -s -- X.Y.Z

Pin a version in CI, development containers, and reproducible setup scripts. The website tracks main and may document changes newer than a pinned executable; labcoat docs --llm is the installed-version reference.

Verify artifact provenance

GitHub publishes build-provenance attestations for every CLI and runtime asset. With the GitHub CLI installed:

gh release download cli-vX.Y.Z --repo jonatns/labcoat --pattern 'labcoat-*'
gh attestation verify ./labcoat-* --repo jonatns/labcoat

The installer verifies the CLI checksum automatically. Runtime downloads are verified against the exact release manifest before installation.

Upgrade or roll back

Run the installer again to atomically replace the executable:

# Upgrade to the latest stable release
curl -fsSL https://labcoat.sh/install | sh

# Roll back to a known version
curl -fsSL https://labcoat.sh/install | sh -s -- X.Y.Z

Confirm the active executable after either operation:

command -v labcoat
labcoat --version
labcoat --help
labcoat binaries

Compilation prerequisites

Contract compilation requires Cargo and LLVM Clang with a WebAssembly backend.

# macOS
brew install llvm

# Debian or Ubuntu
sudo apt install clang wasi-libc

Then run:

labcoat doctor

If $HOME/.local/bin is not on PATH, the installer prints the exact export command to add.

Uninstall

Remove the CLI from the same directory used during installation:

rm "$HOME/.local/bin/labcoat"

This does not remove projects, wallets, chain data, logs, or versioned runtime directories. Review labcoat binaries --verbose and your platform’s Labcoat data directory before removing that data manually.

Runtime and security boundaries

Labcoat Network consists of one Qubitcoin process with Alkanes and Esplorashrew indexer modules. It is local/private and uses an unauthenticated Bitcoin regtest RPC endpoint bound to loopback; it is not Signet. Keep it local and never use production wallet seed phrases with Labcoat.

Labcoat is early-stage software for local Alkanes development. Interfaces may change before 1.0; mainnet deployment controls are not production-ready. Read the security policy and Stability and releases before relying on it.