The right tool version in every project, from one file.
Every project needs its own tools: a language, a build helper, maybe an AI assistant. Setting them up by hand means each person ends up with something slightly different. AIDC fixes that. The project keeps a short list of the tools it needs and the version of each. Anyone who opens the project gets exactly that list.
Picture a new colleague joining a team that builds on one particular release of Node.js. They open the project, ask for its tools once, and are working on the same version as everyone else. A second project on the same machine can use a different version without any clash. AIDC only chooses which installed version you see; it changes nothing else on your machine.
It knows 42 tools out of the box: popular programming languages, the AI assistants people run in a project, and common infrastructure tools. Installing an assistant does not sign you in to it; each assistant keeps its own account.
What you gain over installing tools by hand.
Installing tools with whatever a download page offers gives each person, each container and each build a slightly different result. AIDC keeps the intent in the project and checks what it downloads.
Downloads are checked
A damaged or swapped Hub package is not installed
- Typical alternative
- Running an installer straight from a web page
- Here
- Downloads from the MAIT Hub are compared with the checksum the Hub publishes, and a mismatch is refused before anything is unpacked
One short request installs and selects
A project's tools are one request and one readable file
- Typical alternative
- Download, unpack, adjust your settings, repeat for each project
- Here
- You ask for a tool and a version once; it is installed, written into the project's list and switched on
Your accounts stay yours
Installing a tool grants it nothing
- Typical alternative
- Handing a setup script your sign-in details
- Here
- Installing a tool never signs you in to it, and your MAIT access only opens MAIT features
Every project runs the version it chose
Two projects with different needs never fight over one install
- Typical alternative
- One version shared by every project
- Here
- The project's own list decides, and a nested folder can differ from its parent, or you can try another version in one window
AI assistants are tools like the others
The assistant and the project use the same tools at the same versions
- Typical alternative
- Installing each assistant by hand and tracking its updates
- Here
- Assistants are on the same list, and your own agent can be given a short description of the tools it is working with
You can see and clean up what is installed
A wrong version is found quickly and fixed by changing one line
- Typical alternative
- Guessing from folder contents
- Here
- You can ask what is installed, what is active and what looks wrong, and remove what you no longer use
Already in every MAIT project container.
The MAIT image already includes AIDC, so a project container started by AIDC Launch can install tools straight away. A newer image brings a newer AIDC. Getting tools from their publishers needs no sign-in. MAIT's own package source needs your MAIT sign-in. Tools you have installed keep working offline.
Where it sits in the MAIT toolkit.
Where to read on.
- Install, then Workflows
- Operate and Customize
- Inside AIDC, for sources, checks and the path