mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install aidc

Check the AIDC your project container already has, switch it on in your shell, install a first tool, and sign in if you need MAIT's package source.

Beta
Steps

Six steps from a project container to a pinned tool.

Getting aidc, switching on shell integration and installing a tool are separate steps, and success at one does not prove the next. Check each result before moving on.

  1. Install a supplied executable for your user
    $ mkdir -p "$HOME/.local/bin"
    $ install -m 755 ./aidc "$HOME/.local/bin/aidc"
    $ export PATH="$HOME/.local/bin:$PATH"
    Step 1 of 6

    Find AIDC

    In a project container started by AIDC Launch you already have it, because the MAIT image includes aidc; a newer image brings a newer release. Outside the image, a standalone Linux executable exists only for environments without it. Obtain it from The MAIT Team, through the support page in the portal, or from your environment owner, together with its expected SHA-256 checksum, and compare it with sha256sum ./aidc before you install it. Do not install a file whose origin or checksum you cannot confirm.

    What you get

    An aidc executable on your path, from a source you can name.

  2. Check the executable
    $ aidc version
    $ command -v aidc
    Capturedaidc 3.16.7 · Ubuntu 26.04
    What it prints on Linux
    $ aidc version
    aidc 3.16.7
    $ command -v aidc
    /usr/local/bin/aidc
    Step 2 of 6

    Check that it runs

    version prints aidc and the release. Top-level --version and --help are not accepted; use aidc version and aidc help COMMAND. A version answer shows that the program runs. It does not show that shell integration or any tool works.

    What you get

    The release you are running and the path of the copy your shell finds.

  3. Add the integration to bash
    $ aidc env setup bash
    Capturedaidc 3.16.7 · Ubuntu 26.04
    What it prints
    $ aidc env setup bash
    [ok] Successfully added AIDC integration to /home/user/.profile
    [ok] Successfully added AIDC integration to /home/user/.bashrc
    Step 3 of 6

    Switch on shell integration

    Bash gets .profile and .bashrc; zsh uses .zprofile and fish uses .config/fish/conf.d/aidc.fish, by naming zsh or fish instead. Repeating the command replaces the marked block. Open a new shell, or run source "$HOME/.bashrc", so the integration takes effect.

    What you get

    A shell that puts the active tool versions on its path whenever it enters a project.

  4. Install Node.js 22
    $ cd ~/projects/example-app
    $ aidc install nodejs@22
    Capturedaidc 3.16.7 · Ubuntu 26.04
    What it prints
    $ aidc install nodejs@22
    [ok] Downloaded nodejs 22.23.3 from vendor
    Extracting and installing...
    [ok] Extracted and installed
    Validating installation...
    [ok] Installation validated
    [ok] Successfully installed nodejs 22.23.3
    Location: /home/user/.aidc/installs/nodejs/22.23.3
    Source: vendor
     
    Available commands
    corepack
    node
    npm
    npx
    [ok] Set nodejs 22.23.3 in /home/user/projects/example-app/.aidc.yaml
    [ok] Activated nodejs 22.23.3
    Step 4 of 6

    Install a first tool

    Run this from the project directory. An explicit install records the version in .aidc.yaml in the current directory and activates it, even when the tool was already installed, so look at the file first if the project already has one.

    22 asks for the highest matching release. The output names the release it chose, where it went and which source supplied it. Keep that source line if an install fails.

    What you get

    The tool under ~/.aidc, and a .aidc.yaml that names the release.

  5. Check the selection and the executable
    $ aidc current nodejs
    $ aidc which node
    $ aidc list
    Capturedaidc 3.16.7 · Ubuntu 26.04
    What it prints
    $ aidc current nodejs
    nodejs 22.23.3
    $ aidc which node
    /home/user/.aidc/installs/nodejs/22.23.3/bin/node
    $ aidc list
    nodejs
    22.23.3
    Step 5 of 6

    Check what is active

    current and which read the nearest .aidc.yaml. A temporary aidc use in this shell can make the running tool differ from them, and an alias or function can override the path, so also run command -v node and node --version.

    What you get

    The concrete version the project asks for and the file that will run.

  6. Sign in and check
    $ aidc login
    $ aidc login --check
    Step 6 of 6

    Sign in when you need the Hub

    Ordinary installs from the tool vendors need no sign-in. aidc login stores MAIT credentials that open up the Hub, aidc upgrade, aidc prune and self-update.

    aidc login prints an activation address and asks for the login code the page shows. aidc login --check validates the stored credentials and renews them if your features changed. Without credentials, most commands print one warning line and carry on.

    What you get

    A credentials file for your account, or the knowledge that you do not need one yet.

Next

Where to go next.

  • Workflows, for pinning, trying and automating