Components

Native commands and language CLIs, one 1.2.0 family.

Each one has its own source, digest, and license. They're only considered compatible when that exact set is released together.

What each component does

ait

The main CLI: sprint lineage, isolated Tasks, Snapshots, evidence, recovery, Git interop, and closeout.

ait-server

The remote protocol and shared durable state. It installs inactive and starts only when you say so.

ait-runner

Runs typed jobs from the server against the CI entrypoint your repository declares.

ait-python

The Python ait CLI and direct PyO3 API ship in PyPI ait-native. The language entrypoint calls typed Rust APIs; the wheel contains no standalone native CLI, Server or Runner executable.

ait-node

The direct in-process Node-API binding, plus the npm packaging. The JS/TS API loads the matching platform addon, and its ait command calls that same binding without spawning an external process.

One product across install channels

Native bundles

Homebrew, apt and WinGet use the ait-native product identity and bundle ait, ait-server and ait-runner. See Release Status for each channel’s actual availability.

Python

PyPI ait-native supplies the Python ait entrypoint and loadable binding. It does not bundle Server or Runner.

Node.js

npm @wa120/ait-native supplies the JavaScript ait CLI and direct Node-API binding. Platform packages are its dependencies, not separate products.

What they all share

Retired public chat components

ait-agent and ait-agent-worker are excluded from the 1.2.0 public family. Their source, licenses and history remain; Agent Teams and the core language bindings remain supported. Historical component tables do not restore chat support.

Install what you need

Quickstart lists the ways to get 1.2.0; Release Status shows where every public channel stands.