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.
- $ 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 withsha256sum ./aidcbefore you install it. Do not install a file whose origin or checksum you cannot confirm.What you getAn
aidcexecutable on your path, from a source you can name. - $ aidc version$ command -v aidcCapturedaidc 3.16.7 · Ubuntu 26.04$ aidc versionaidc 3.16.7$ command -v aidc/usr/local/bin/aidcStep 2 of 6
Check that it runs
versionprintsaidcand the release. Top-level--versionand--helpare not accepted; useaidc versionandaidc help COMMAND. A version answer shows that the program runs. It does not show that shell integration or any tool works.What you getThe release you are running and the path of the copy your shell finds.
- $ aidc env setup bashCapturedaidc 3.16.7 · Ubuntu 26.04$ aidc env setup bash[ok] Successfully added AIDC integration to /home/user/.profile[ok] Successfully added AIDC integration to /home/user/.bashrcStep 3 of 6
Switch on shell integration
Bash gets
.profileand.bashrc; zsh uses.zprofileand fish uses.config/fish/conf.d/aidc.fish, by namingzshorfishinstead. Repeating the command replaces the marked block. Open a new shell, or runsource "$HOME/.bashrc", so the integration takes effect.What you getA shell that puts the active tool versions on its path whenever it enters a project.
- $ cd ~/projects/example-app$ aidc install nodejs@22Capturedaidc 3.16.7 · Ubuntu 26.04$ aidc install nodejs@22[ok] Downloaded nodejs 22.23.3 from vendorExtracting and installing...[ok] Extracted and installedValidating installation...[ok] Installation validated[ok] Successfully installed nodejs 22.23.3Location: /home/user/.aidc/installs/nodejs/22.23.3Source: vendorAvailable commandscorepacknodenpmnpx[ok] Set nodejs 22.23.3 in /home/user/projects/example-app/.aidc.yaml[ok] Activated nodejs 22.23.3Step 4 of 6
Install a first tool
Run this from the project directory. An explicit install records the version in
.aidc.yamlin 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.22asks 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 getThe tool under
~/.aidc, and a.aidc.yamlthat names the release. - $ aidc current nodejs$ aidc which node$ aidc listCapturedaidc 3.16.7 · Ubuntu 26.04$ aidc current nodejsnodejs 22.23.3$ aidc which node/home/user/.aidc/installs/nodejs/22.23.3/bin/node$ aidc listnodejs22.23.3Step 5 of 6
Check what is active
currentandwhichread the nearest.aidc.yaml. A temporaryaidc usein this shell can make the running tool differ from them, and an alias or function can override the path, so also runcommand -v nodeandnode --version.What you getThe concrete version the project asks for and the file that will run.
- $ aidc login$ aidc login --checkStep 6 of 6
Sign in when you need the Hub
Ordinary installs from the tool vendors need no sign-in.
aidc loginstores MAIT credentials that open up the Hub,aidc upgrade,aidc pruneand self-update.aidc loginprints an activation address and asks for the login code the page shows.aidc login --checkvalidates the stored credentials and renews them if your features changed. Without credentials, most commands print one warning line and carry on.What you getA credentials file for your account, or the knowledge that you do not need one yet.
Where to go next.
- Workflows, for pinning, trying and automating