Skip to main content

​
Aient CLI

The aient command runs local development work in isolated remote sandboxes. This guide documents Aient CLI 0.7.0, available as a static binary for macOS and Linux on Intel and Arm.

Authentication and projects

Keep separate customer sessions and bind each checkout to the intended Aient profile.

Environment secrets

Set or replace an encrypted environment secret without exposing its value in a command line.

Run and synchronise

Run a local Git worktree remotely or synchronise its exact state into a retained sandbox.

Retained sandboxes

Create, inspect, reuse, enter, and delete sandboxes.

Executions and files

Observe live commands and transfer explicit files.

​
Install and verify

Download the current release from the Aient CLI release repository. Follow the repository’s installation and verification guide before placing the binary on your PATH. Each release includes static archives, SHA-256 checksums, SPDX SBOMs, Sigstore verification bundles, and SLSA provenance. GitHub-generated source archives are documentation only; they are not verified Aient CLI release artifacts.

​
Quick start

From a local Git checkout:
With --environment, the CLI synchronizes the current workspace by default. It shows the organisation, resolved environment, inferred or selected repository, and brokered GitHub capabilities before creating the sandbox.
The local checkout is the workspace source. A configured Git remote is only a repository selector. The Aient service verifies membership, environment policy, repository ownership, and the active GitHub App installation before granting any provider operation.
An organisation administrator must enable customer CLI workspaces for the selected environment. If it is disabled, the command fails before sandbox creation with HTTP 403: development environment is not enabled for CLI workloads.

​
Choose a workflow

Use sandbox run for a disposable command:
Use --keep when you want to retain the created, environment-bound sandbox:
In 0.7.0, an environment-bound customer sandbox can be reused only through selector-bearing sandbox exec and sandbox execution commands, found with sandbox list --environment, and removed by its owner with sandbox delete. sandbox sync, files, shell, status, wait, and logs cannot reopen that bound sandbox. To transfer changed local state, delete it and start a fresh sandbox run --keep. Commands without --environment operate without environment or repository capabilities.

​
Current limitations

The commands documented in this section are the surface shipped in Aient CLI 0.7.0.
  • Commands cannot be deliberately detached. sandbox execution attach can follow an already-known live execution, but output is not retained for replay.
  • sandbox shell always opens a new shell. Shell reattachment and shell history are unavailable.
See Current limits and troubleshooting for recovery guidance and common errors.