Aient CLI

The aient command runs a local workspace in an isolated Aient sandbox. This repository is the customer-facing binary distribution channel; it intentionally does not contain the private CLI source.

The current invited-preview release is 0.7.0 for macOS and Linux on Intel and Arm. Each release includes:

• one static aient archive for each supported platform;
• SHA-256 checksums;
• SPDX JSON SBOMs;
• Sigstore verification bundles; and
• SLSA provenance tied to Aient's private build workflow.

Git 2.45 or newer enables retained-workspace incremental synchronization for partial/promisor clones without lazy object fetching. Ordinary repositories also use incremental synchronization on older Git clients; an older partial clone uses the complete-snapshot transfer path.

GitHub automatically adds “Source code (zip)” and “Source code (tar.gz)” to every release. Those archives contain only this public documentation skeleton. They are not Aient CLI source, are not listed in checksums.txt, and are not verified release artifacts.

Install on macOS or Linux

Set the release version and select the archive for your machine:

VERSION=0.7.0
case "$(uname -s)-$(uname -m)" in
  Darwin-x86_64) TARGET=darwin_amd64 ;;
  Darwin-arm64) TARGET=darwin_arm64 ;;
  Linux-x86_64) TARGET=linux_amd64 ;;
  Linux-aarch64|Linux-arm64) TARGET=linux_arm64 ;;
  *) echo "Unsupported platform: $(uname -s)-$(uname -m)" >&2; exit 1 ;;
esac

TAG="aient-cli-v${VERSION}"
ARCHIVE="aient_${VERSION}_${TARGET}.tar.gz"
BASE="https://github.com/aient-ai/aient-cli/releases/download/${TAG}"
RELEASE_DIR="$(mktemp -d)"
curl -fsSL "${BASE}/${ARCHIVE}" -o "${RELEASE_DIR}/${ARCHIVE}"
curl -fsSL "${BASE}/checksums.txt" -o "${RELEASE_DIR}/checksums.txt"
curl -fsSL "${BASE}/checksums.txt.sigstore.json" \
  -o "${RELEASE_DIR}/checksums.txt.sigstore.json"

curl is deliberate on macOS: it avoids the browser quarantine attribute that would otherwise block this currently unnotarised preview binary. Verify the signed checksum manifest before trusting the downloaded archive:

cd "${RELEASE_DIR}"
cosign verify-blob \
  --bundle checksums.txt.sigstore.json \
  --certificate-identity \
    "https://github.com/haf/glimt/.github/workflows/aient-cli-release.yml@refs/tags/${TAG}" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

if command -v sha256sum >/dev/null 2>&1; then
  grep "  ${ARCHIVE}$" checksums.txt | sha256sum -c -
else
  grep "  ${ARCHIVE}$" checksums.txt | shasum -a 256 -c -
fi

Install without requiring Python, Node.js, uv, or a package manager:

tar -xzf "${ARCHIVE}"
mkdir -p "${HOME}/bin"
install -m 0755 aient "${HOME}/bin/.aient.new"
mv "${HOME}/bin/.aient.new" "${HOME}/bin/aient"
"${HOME}/bin/aient" version

Ensure ${HOME}/bin is on PATH. Upgrade by repeating the download, verification, and atomic install with a newer published version. Published release assets are immutable; Aient fixes a bad release with a new version.

Install the agent skill

Install the customer CLI workflow skill in the current agent project:

npx skills add aient-ai/aient-cli --skill use-aient-cli

Install it globally for Codex:

npx skills add aient-ai/aient-cli \
  --skill use-aient-cli \
  --agent codex \
  --global \
  --yes

The skill covers customer OAuth profiles, project selection, exact workspace synchronization, retained execution recovery, and current public command boundaries. Native Aient Harness agents already have sandbox tools and should not create nested CLI sandboxes.

Verify SLSA provenance

For the full build-provenance check, also download multiple.intoto.jsonl and run:

curl -fsSL "${BASE}/multiple.intoto.jsonl" \
  -o "${RELEASE_DIR}/multiple.intoto.jsonl"
cd "${RELEASE_DIR}"
slsa-verifier verify-artifact "${ARCHIVE}" \
  --provenance-path multiple.intoto.jsonl \
  --source-uri github.com/haf/glimt \
  --source-tag "${TAG}"

The verified source and workflow identity is haf/glimt, while this public repository is only the byte-for-byte release host. That distinction is intentional; see Security.

Start a customer session

The default profile uses customer OAuth and never asks for an operator API key:

aient auth login
aient auth status
aient sandbox run --environment development -- go test ./...
aient sandbox exec retained-sandbox --workdir /workspace/repo -- go test ./...
aient auth logout

auth login opens the Aient consent flow in your browser. An administrator must first enable customer CLI development on the selected environment. The current preview supports repository-independent and verified-repository development, including brokered environment/GitHub capabilities for sandbox run and retained sandbox exec. It may infer a repository selector from local Git remotes, but the server verifies authority; a configured remote never grants access. Retained sandbox exec prints an execution UUID, streams live output, and can reconcile transport loss through sandbox execution attach|status|wait|cancel without replaying the command. Use one active terminal per execution: a second live attachment supersedes the first, and output received by either attachment is not replayed to the other. This is not durable detach: an unobserved connection-bound execution is cancelled after its short server-owned grace. sandbox run remains buffered, and each sandbox shell opens a fresh non-resumable PTY without brokered environment/GitHub capabilities.

Organisation owners and administrators can set or replace an encrypted environment secret after consenting to the dedicated write capability:

aient --profile cope auth login
printf '%s' "$STRIPE_SECRET_KEY" |
  aient --profile cope environment secrets set \
    --environment development \
    STRIPE_SECRET_KEY \
    --stdin

The profile selects the organisation and --environment is required. Secret values are never returned by the command. Setting a secret is separate from enabling customer CLI workloads and from deciding which environment capabilities are sandbox-exportable.

For help, contact support@aient.ai.