ait
The main CLI: sprint lineage, isolated Tasks, Snapshots, evidence, recovery, Git interop, and closeout.
Components
Seven components, released as one 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-agent
Optional. Configures and supervises transport workers you've explicitly chosen to run.
ait-agent-worker
Optional. Runs the Telegram, LINE, Discord, and Slack workers. It isn't a replacement for your coding client.
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 binding you can call directly from your code. It ships inside the PyPI ait-native package.
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 bundle and Python
Homebrew, apt, and PyPI use the ait-native name. PyPI also gives you the Python binding.
Node.js
On npm, @wa120/ait-native is the package to install. The platform packages are its dependencies, not products of their own.
What they all share
- The same behavior no matter what language your repository is in.
- Sprint items bound to exact Markdown, and worktrees owned by their Task.
- Snapshots, check evidence, recovery, and Git interop.
- Versioned server and runner protocols for remote work you've configured.
- Optional transport management through
ait-agentandait-agent-worker. - Optional in-process Python and Node.js entry points.
Install what you need
Quickstart lists the ways to get 1.1.1; Release Status shows where every public channel stands.