AIDC Launch (aidcx): Install aidcx

AIDC Launch (aidcx)

Use the native host terminal for launcher installation, login and install. On macOS or Windows, enter aidcx terminal after preparation and run doctor and project commands there; the native host refuses those operational commands. Clone the project in the Linux home, which is separate from the Mac home.

Steps

Five steps from a clean machine to a shell in your project.

Installing the launcher, signing in, preparing the runtime and starting are separate steps, and success at one does not prove the next. Check each result before moving on.

Install aidcx
$ sh -c "$(curl -fsSL https://dist.mait.sh/aidcx-installer/sh/all)"
Step 1 of 5
Install the launcher
Run the installer for your system. Both use the stable channel by default; use the channel approved for your environment rather than swapping in a development build to get past an error.
On Linux and macOS the launcher goes to $HOME/.local/bin/aidcx; a persistent AIDCX_INSTALL_DIR changes the directory. On Windows, the installer selects the Microsoft Store package and rejects AIDCX_WINDOWS_PACKAGE=exe.
The Windows channel selects the product: mait.sh for stable, mait.sh (beta) or mait.sh (edge). They all provide aidcx.exe, so install only one channel. Installation requires access to the approved Store product. If access is unavailable, resolve the account or organization-policy restriction with your administrator before continuing. Installing the package does not prepare the runtime; step 4 still applies. Follow install and update from the Microsoft Store.
What you get
The launcher on your computer and its folder added to your shell path.
Check the launcher
$ aidcx version
$ command -v aidcx
Capturedaidcx 6.15.7 · Ubuntu 26.04
What it prints on Linux
$ aidcx version
aidcx 6.15.7
$ command -v aidcx
/home/user/.local/bin/aidcx
Step 2 of 5
Check that it runs
Open a new terminal so the path is picked up, then ask the launcher for its version and where it lives.
A version answer shows that this executable runs. It does not show that Docker, the virtual machine or the project container work.
What you get
A version number and the path of the copy you will run and update.
Sign in
$ aidcx login
$ aidcx login --check
Step 3 of 5
Sign in
Follow the URL and code that this run prints; do not reuse a code from documentation. The check loads the stored credential and tries to renew it. A successful login stores your MAIT access on this machine. It does not sign you in to the agent's own account.
What you get
A stored MAIT credential. Starting a container additionally needs the launcher feature on that credential.

Prepare the runtime

$ aidcx install

System	Supported host	What `aidcx install` prepares
Linux	x86_64 or arm64 with systemd, on a Debian or Ubuntu, RHEL or Fedora, or Arch family distribution. On Arch the secure runtime is available on x86_64 only	Docker Engine and the secure runtime on the host
macOS	Apple Silicon only, with at least 8 GiB of memory	A managed Linux virtual machine
Windows	Windows with WSL2 available, with at least 8 GiB of memory	A managed WSL2 distribution named `Mait`

Capturedaidcx 6.15.7 · Ubuntu 26.04, trimmed

doctor on a new machine

$ aidcx doctor

running 11 checks

Platform

[ok] OS — linux

[ok] Arch — x86_64

[ok] aidcx binary — /home/user/.local/bin/aidcx

Container Runtime

[error] Docker unavailable — the Docker daemon is not reachable

Suggestion: run `aidcx install`

Credentials

[warn] Credentials not found — /home/user/.mait/credentials

Updates

[ok] Up to date — 6.15.7

Connectivity

[ok] Login service reachable

[fail] 1 error, 7 warnings

Step 4 of 5

Prepare the runtime

Runtime preparation needs the credential from step 3. On native Linux, optionally run aidcx doctor first. On macOS and Windows, prepare from the native terminal and enter Linux afterward; native doctor is refused.

What the install prepares depends on the system:

On native Linux, aidcx doctor reports what is missing and what to do about it. This is a trimmed capture from a fresh Ubuntu 26.04 machine before the install:

Warnings about display relays, a missing bridge or the kvm group do not block a first start. The error does, and the install fixes it.

Run aidcx install as yourself and let it ask for elevation where a step needs it; do not put sudo in front of the whole command. After it finishes on macOS or Windows, open aidcx terminal and run aidcx doctor inside Linux; native doctor is refused. On Linux, run doctor in your existing terminal. Read the runtime findings: an install can finish with work remaining. Docker Desktop cannot run the secure runtime and is refused.

What you get

A host that aidcx doctor reports as ready for the secure runtime.

Start and enter the container
$ cd /path/to/project
$ aidcx scaffold
$ aidcx start --trusted
$ aidcx shell
Check inside the container
$ pwd
$ ls
$ printf 'aidcx-shell-ready\n'
Step 5 of 5
Start your project and open a shell
In the project directory, reuse the project's reviewed MAIT configuration, or write one with aidcx scaffold. On macOS and Windows, open aidcx terminal first and use a repository cloned into that Linux session. On macOS its home directory is separate from your Mac home, even if the path text matches. Then start and enter:
--trusted records that you reviewed this project; grant it only after you have. Inside the shell, check that you are in the project you meant to open:
What you get
The marker prints and the files are your project's. Run your agent CLI from here; exit leaves the shell and aidcx stop stops the container.

Result

A prepared host and a shell in a secure container.

AIDC Launch is installed, signed in, the runtime is prepared and your project runs in a secure container. If a step fails, repeat that step, not all of them: Troubleshooting is organised by the stage that fails.

Install aidcx

Five steps from a clean machine to a shell in your project.

Install the launcher

Check that it runs

Sign in

Prepare the runtime

Start your project and open a shell

A prepared host and a shell in a secure container.

Where to go next.