Install

For most users, install the published binary. That keeps the setup path short and matches the public story.

• Use OTA_VERSION for released proof.
• Use OTA_GIT_REV when you need deterministic unreleased proof on one exact commit.
• Use OTA_GIT_BRANCH only for active pressure testing, because it follows a moving branch tip.

curl -fsSL https://dist.ota.run/install.sh | sh

curl -fsSL https://dist.ota.run/install.sh | OTA_VERSION=vX.Y.Z sh

curl -fsSL https://dist.ota.run/install.sh | OTA_GIT_BRANCH=1.6.21-implementation sh -s -- --from-git

irm https://dist.ota.run/install.ps1 | iex

$env:OTA_VERSION = "vX.Y.Z"irm https://dist.ota.run/install.ps1 | iex

$env:OTA_GIT_BRANCH = "1.6.21-implementation"& ([scriptblock]::Create((irm https://dist.ota.run/install.ps1))) -FromGit

Use the source install path when you are working from a cloned checkout.

./scripts/install.sh --from-source

powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 -FromSource

• Confirm the binary is available with ota --version.
• Use ota --version --json when CI or tools need explicit build provenance (semver, source_build, commit, dirty) plus schema_version and contract_capabilities.
• Treat schema_version as the coarse contract-generation marker and contract_capabilities as the additive feature-support catalog.
• Run ota doctor in a repo before you write or execute tasks.
• Use ota validate --help to confirm the CLI is available and responsive.

ota --versionota --version --jsonota doctor --plainota validate --help

Install the skill after ota is already on PATH and the binary verifies cleanly.

The source of truth lives in ota-run/skills, and ota skills install writes that first-party distribution into the selected agent skill directory.

ota skills install --agent codex

ota skills install --agent claude