Skip to content

Install Runtime

Goal: install the engrt binary and confirm it runs.

Engineering Runtime is a single binary with embedded command help and contracts. You do not need Go or a source checkout. Native tools such as gh, kubectl and gcloud are needed only for operations that use them.

Requirements

v0.14.0 was released November 17, 2026. The qualified platform set is macOS, Linux and Windows on amd64 and arm64. The binary is engrt (engrt.exe on Windows); see Upgrading.

Quick install (macOS or Linux)

curl -fsSL https://raw.githubusercontent.com/engineeringruntime/engineering-runtime-releases/main/install.sh | sh
engrt version

The installer selects your platform archive, verifies it against the release's SHA256SUMS.txt and installs engrt. Set VERSION=v0.14.0 to pin a release and INSTALL_DIR to choose the destination.

Without INSTALL_DIR the installer uses /usr/local/bin when it is writable, otherwise ~/.local/bin (created if needed). Make sure the chosen directory is on your PATH; command -v engrt shows which one you got.

Each release's notes, archives and SHA256SUMS.txt are on the release downloads page. Checksums prove the download is intact; they do not prove who published it.

Obtain the release

Download your platform archive and SHA256SUMS.txt from the release downloads. If you have trouble accessing the release or installation artifacts, contact the Engineering Runtime project.

The v0.14.0 macOS/Linux archive set is:

Platform Architecture Archive
macOS Apple Silicon engrt-v0.14.0-darwin-arm64.tar.gz
macOS Intel engrt-v0.14.0-darwin-amd64.tar.gz
Linux x86_64 engrt-v0.14.0-linux-amd64.tar.gz
Linux arm64 engrt-v0.14.0-linux-arm64.tar.gz

Each archive contains a versioned directory with engrt, README.md and reference commands/, configs/ and schemas/. The binary uses embedded contracts; it does not install the archive's reference configuration as policy.

Install with Homebrew (macOS or Linux)

brew install engineeringruntime/tap/engineering-runtime
engrt version

The fully qualified package name selects the tap automatically. The formula downloads the same versioned archive and verifies the same published SHA256 as the manual steps below. It supports macOS (Apple Silicon and Intel) and Linux (amd64 and arm64).

brew upgrade engineeringruntime/tap/engineering-runtime     # move to the latest release
brew uninstall engineeringruntime/tap/engineering-runtime   # remove only the Homebrew-managed binary

Use the full name in every brew command. Since Homebrew 7, a formula from a third-party tap loads only once it is trusted. Installing, upgrading or reinstalling it by the full name trusts it, while a short name such as brew upgrade engineering-runtime is refused with Refusing to load formula … from untrusted tap until then. To trust it explicitly, run brew trust --formula engineeringruntime/tap/engineering-runtime.

brew uninstall leaves ~/.engrt (Runtime Home) intact. If a previous manual install is also on PATH, see If another runtime wins on PATH below — the same precedence rule applies regardless of which install method is first.

Install manually

Work in the directory containing the downloaded archive and checksum file. The example installs v0.14.0 on Apple Silicon; set VERSION, OS and ARCH to your archive.

VERSION=v0.14.0
OS=darwin                       # darwin for macOS; linux for Linux
ARCH=arm64                      # arm64 or amd64
ARCHIVE=engrt-$VERSION-$OS-$ARCH.tar.gz

Verify the matching checksum before extraction. Require exactly one entry for your selected archive; do not treat unrelated missing archives as corruption.

awk -v name="$ARCHIVE" '$2 == name { print; count++ } END { if (count != 1) exit 1 }' \
  SHA256SUMS.txt > selected-checksum.txt

On macOS:

shasum -a 256 -c selected-checksum.txt

On Linux:

sha256sum -c selected-checksum.txt

Continue only if verification succeeds. Extract and install in a directory you own:

tar -xzf "$ARCHIVE"
mkdir -p ~/.local/bin
install -m 0755 "engrt-$VERSION-$OS-$ARCH/engrt" ~/.local/bin/engrt
export PATH="$HOME/.local/bin:$PATH"
engrt version

Retain the PATH setting in your shell configuration if needed. On macOS, if the OS blocks a downloaded binary, confirm its source and checksum before following your organization's approval process.

If another runtime wins on PATH

command -v engrt
~/.local/bin/engrt version
engrt version

If versions differ, put the intended install directory first on PATH and start a new shell. Remove an older binary only after confirming its exact path. Do not delete Runtime Home to resolve a PATH conflict.

Verify the install

engrt bootstrap
engrt config validate

Bootstrap refreshes release-owned contracts in Runtime Home. It creates no user configuration, policy, native credentials or capability definitions. Diagnostics may probe admitted native authentication without switching provider context.

CI installation

Provision the same checksum-verified binary on a supported macOS/Linux runner. Pin its version, create an isolated Runtime Home per job, and follow CI/CD for authentication and execution.

Common failures

  • Missing archive/access: contact the project.
  • Checksum mismatch: stop and obtain a verified copy; do not install it.
  • engrt: command not found: check PATH and the install directory. Releases before v0.10.0 installed runtime instead.
  • Windows: use the v0.14.0 ZIP matching your native architecture; v0.9.9 has no supported Windows archive.

Uninstall

Inspect command -v engrt, then remove only the binary you installed. Keep Runtime Home if you need its contracts, audit history or recovery state. Removing external configuration or capabilities is a separate action.

Windows installation

v0.14.0 has passed native qualification on Windows amd64 and arm64. Download the published ZIP from the release downloads. v0.9.9 has no supported Windows archive.

PowerShell installer

Use PowerShell 7 or later (pwsh). A stock Windows machine has only Windows PowerShell 5.1 (powershell.exe), where the script stops at its #requires line. Install PowerShell 7 first, then open a new pwsh terminal:

winget install --id Microsoft.PowerShell --source winget

Then:

$ErrorActionPreference = 'Stop'
Invoke-WebRequest https://raw.githubusercontent.com/engineeringruntime/engineering-runtime-releases/main/install.ps1 -OutFile install.ps1
./install.ps1 -Version v0.14.0
$env:PATH = "$HOME\.local\bin;$env:PATH"
engrt version

The script chooses native x64 or Arm64, checks the ZIP checksum and executable version, and installs engrt.exe in ~/.local/bin. Add that directory to your user PATH for future terminals. It preserves Runtime Home and any earlier runtime.exe; it does not migrate settings or edit persistent PATH.

Omit -Version for Latest; use -InstallDirectory for another destination. VERSION and INSTALL_DIR environment variables are supported. Offline installation uses -Version v0.14.0 -ArchiveDirectory <folder> with the native ZIP and SHA256SUMS.txt. Stable v0.10.0 and later are supported. -GitHubCLI downloads through an authenticated gh instead of public HTTPS. A failed checksum or executable-version check preserves an existing installation; the version probe uses a disposable Home.

Manual ZIP installation

Download the matching engrt-v0.14.0-windows-amd64.zip or engrt-v0.14.0-windows-arm64.zip and its SHA256SUMS.txt from the release downloads. In PowerShell 7, select your architecture and verify exactly one checksum entry before extracting into a new directory:

$version = 'v0.14.0'
$arch = 'arm64' # Use amd64 for x64 Windows.
$package = "engrt-$version-windows-$arch"
$archive = "$package.zip"
$entries = @(Get-Content SHA256SUMS.txt | Where-Object { $_ -match ('^[0-9a-fA-F]{64} [ *]' + [regex]::Escape($archive) + '$') })
if ($entries.Count -ne 1) { throw 'Missing or ambiguous checksum entry' }
if ((Get-FileHash -Algorithm SHA256 $archive).Hash -ine $entries[0].Substring(0, 64)) { throw 'Checksum mismatch' }
$destination = Join-Path $PWD ('engrt-install-' + [guid]::NewGuid().ToString('N'))
Expand-Archive -LiteralPath $archive -DestinationPath $destination
$binary = Join-Path $destination "$package/engrt.exe"
& $binary version
if ($LASTEXITCODE -ne 0) { throw 'Release executable did not run' }

The version must be engrt 0.14.0. Put the verified engrt.exe in a directory you own and add that directory to PATH. Use Get-Command engrt -All to check which executable wins. No runtime alias ships. The shell installer and Homebrew are separate macOS/Linux paths.

The default Home is $HOME/.engrt; use $env:ENGRT_HOME for an explicit isolated Home. Old RUNTIME_* variables and ~/.engineering-runtime are not aliases or automatically migrated. Keep earlier Home/evidence for a deliberate rollback; use the earlier binary with a separate Home.

Rollback to an earlier release

The v0.10.0 shell installer refuses pre-0.10.0 VERSION pins with exit 1 before archive downloads or destination writes. For rollback to v0.9.9, use that release's checksum-verified engineering-runtime-* archive and runtime binary in a separate destination and Home. It does not overwrite engrt or migrate existing evidence.

Next

Quick Start

Operational examples on this site were verified against Runtime 0.14.0. After bootstrap, the version-exact files in Runtime Home win.