Run project commands and aidcx doctor in a Linux terminal. On macOS or Windows, prepare the runtime with native aidcx install, then open aidcx terminal and use a project cloned in that Linux environment. Native installation, update and uninstall remain host commands; macOS aidcx bridge also runs on the Mac.
Find your containers and read their state.
Containers are found by project. aidcx list shows every container for the project's repository, including worktree-backed ones and worktrees whose container was deleted.
| Command | Use it to | What it reports |
|---|---|---|
aidcx list | Find a container | Name, id, branch, status, whether it is a worktree, its path, git state, runtime and bound ports. RUNTIME reads secure for every container this release creates |
aidcx inspect | See how a container was set up | Each runtime option with where its value came from: a flag, another flag, host detection or the project default, plus mounts and sizes |
aidcx health | Check a running container now | CPU, memory, processes, filesystem, workspace, credential sharing, bridges, volumes, and a short advisory audit |
aidcx logs | Read the start journal | The in-container journal saved by aidcx start --debug; --docker adds the inner Docker service |
When more than one container could match, AIDC Launch asks you to pick on a terminal and lists the valid values otherwise. To name one directly, use --branch, --name or --id, written as aidcx list shows them.
One report for the host and the runtime.
aidcx doctor reports the platform, memory, the managed virtual machine on a Mac, credential sharing, the container runtime, display, devices, bridges, and available updates. Give it a project path and it adds a row for each runtime option. It still works when the MAIT services are unreachable.
| Exit code | Meaning |
|---|---|
| 0 | No error was reported; warnings can remain |
| 1 | At least one error that is not about the secure runtime |
| 10 to 14 | The secure runtime is not provisioned, the host cannot run it, the secure runtime is missing or incapable, or a stale Docker socket is mounted |
Read the individual findings rather than the totals. A clean report does not show that your workload runs: start the project and run its smallest task.
Stop, delete and prune without losing work.
| Command | What it does | Keep in mind |
|---|---|---|
aidcx stop | Shuts the container down in order (your optional pre-stop command, the inner Docker, systemd, then the container) and keeps it | exit from a shell does not stop the container. Exit code 3 means it stopped, but only by force |
aidcx delete | Deletes the container and tries to remove its image and its own volumes | Always asks Delete NAME (ID12)? [y/N]; --force skips only that question. --keep-volumes keeps the named volumes. A dirty or unpushed worktree needs your answer |
aidcx gc | Cleans the Docker daemon inside a running container: dangling images, old build cache and unused volumes | Shows the plan first. -a and --containers ask you to type the container name. |
aidcx prune | Offers stopped containers and orphan worktrees as a checklist | Running containers are never offered. A clean, pushed worktree is pre-checked; a dirty one is not. The Git branch is never deleted |
Before deleting, copy out any work that lives only in the container.
stop and delete never preselect rows in the multi-container picker. With one eligible container, stop acts on it and delete asks for confirmation. With several candidates, a picker opens with every row unchecked (space toggles, a checks all, n clears, q cancels), and --all acts on every candidate without a picker. Every message names a container as NAME (ID12), the two values aidcx list shows.
A container with its own Docker daemon (--dockerd on) collects stopped builds, dangling images and build cache that nothing else removes, and can consume disk capacity that other environments also need. With a current MAIT image, scheduled cleanup runs every 4 hours by default for a container with its own daemon. It keeps stopped containers, named volumes and tagged images. With fresh persisted history, the first completed scheduled run only reports; an executable update does not reset that history. Labels protect eligible image, container and volume classes; build cache has separate controls. aidcx gc runs cleanup manually, while aidcx health and aidcx inspect show the last run. Keep these procedures on --dockerd on; scheduled cleanup is disabled for --dockerd host. Review the plan and preserve needed data before applying it. Details are in Cleaning the nested Docker daemon.
Update the launcher and repair or remove the runtime.
aidcx update updates the launcher and its managed components: on a Mac and on Windows it also refreshes the launcher inside the virtual machine or distribution. On Windows, --full-image replaces the guest system image, including Linux-home and project files stored there. Back up those files outside the managed Linux installation before running it; preservation of a separate Docker data volume does not preserve the Linux home. On macOS, it runs repair preparation while retaining an existing VM disk. After an update, run aidcx version and command -v aidcx to confirm which copy runs. On Windows, a launcher installed from the Microsoft Store is updated by the Store: use Library > Get updates, or aidcx update --host-only in an interactive terminal, which asks the Store to update it and needs no MAIT sign-in. From a session without a desktop, such as SSH, the Store cannot show its prompt and the update reports Canceled.
| Command | Use it to |
|---|---|
aidcx install --repair | Redo eligible steps when managed state or files are damaged. On macOS it retains an existing VM disk; on Windows it can replace the Linux system image, so back up Linux-home and project files first |
aidcx uninstall | List what would be removed. Add --force to remove the items recorded for your user. Never run it with sudo |
aidcx relay status | Check the display and sound relays on Linux; restart and reap fix them |
On macOS, aidcx uninstall --force leaves the managed virtual-machine disk in place. On Windows, removing the recorded managed distribution deletes its guest files; copy required work out first. Settings and MAIT credentials have separate removal steps. The host maintenance reference lists the extra steps to remove everything.