All docs
Operate
Install and upgrade
Installing aiL as a resident service, pairing each machine, upgrading and rolling back.
aiL binaries are not public yet. This page describes how installation and upgrades work, to be followed once they are released.
What ships
One executable per platform: ail-windows-x64.exe and ail-linux-x64. The install, upgrade and rollback scripts are embedded in the executable and run through ail setup; the target machine needs no extra runtime. A Client that hosts claude, codex or pi also needs Node, because their adapters start through npx.
Directories
| Windows | Linux | |
|---|---|---|
| State directory | %LOCALAPPDATA%\ail\ |
~/.local/share/ail/ |
| Executable | <state directory>\bin\ail.exe, added to the user's PATH |
<state directory>/bin/ail, linked to ~/.local/bin/ail |
| Desk data | <state directory>\desk\ |
<state directory>/desk/ |
| Plugin directory | Given with --plugins when the Daemon is installed |
Same |
Installing
The Desk (one machine of your choice):
ail setup desk --listen 100.64.0.10:8040It places itself in the state directory, initialises its data, installs itself as a resident service and starts. Give
--listenan address on a private network: the Desk has no login and must not be exposed to the public internet.Each Client: issue a pairing code on the Desk's Config page, then run on that Client
ail setup daemon --desk http://100.64.0.10:8040 --code <pairing code> --client-id studio-pc --plugins ~/ail/pluginsOpen the Desk's address in a browser and, on the Config page, choose which Client holds the main repository.
How it stays resident:
| System | How |
|---|---|
| Windows | Task Scheduler, triggered at logon, no administrator rights; restarted automatically after an abnormal exit |
| Linux | systemd system units ail-desk.service and ail-daemon.service, with Restart=always |
To keep a second installation on the same machine, add --instance <name> to ail setup: the state directory and the service names carry that name.
Upgrading and rolling back
ail setup upgrade <new executable>
ail setup rollback
ail setup remove
- An upgrade replaces only the executable; data in the state directory and the plugin directory are untouched.
- Order across machines. Upgrade the machines that run only a Daemon first and the Desk's machine last; roll back in the reverse order. Other orders still stay connected: a new Desk does not send an old Daemon requests it does not know.
- The database. Its structure is upgraded version by version when the Desk starts. If the new version changes the structure, the database is backed up automatically before the upgrade. If a rollback finds that the previous version cannot read the current database, it does not roll back; the error says where the backup is and what restoring it would lose, and you decide whether to add
--restore-backup. - Turns in progress during an upgrade are recorded as failed, and afterwards the engine asks the Worker to continue.
ail setup removeremoves the resident service and keeps the state directory and the plugin directory.
To check: run ail status (connected) and ail version (the same version) on each machine.