What it uses
Which versions does this project use?
You are about to have the agent build or test a project, and you want to be sure it uses the tool versions the project asks for.
Illustrative conversation
YouWhich tool versions is this project using?
Tool callaidc_query { "action": "current" }
What happensOne line per tool with its declared version, such as nodejs 26.10.0, kubectl 1.37.1, helm 4.3.0 and playwright 1.63.0, then the declared system packages.
AgentThe project is on Node.js 26.10.0, kubectl 1.37.1, helm 4.3.0 and Playwright 1.63.0, with its system packages declared alongside.
Find versions
Which versions of a tool exist?
You want to know which versions of a tool are on your machine, which one is in use, and where it lives.
Illustrative conversation
YouWhich versions of kubectl do I have, and where does helm live?
Tool callaidc_query { "action": "describe", "tool": "kubectl" }
What happensTwo versions are installed, 1.37.1 marked active and 1.35.3, with their install path and the available command, kubectl.
Tool callaidc_query { "action": "locate", "tool": "helm" }
What happensThe install directory of the active helm version under the AIDC data directory.
AgentYou have kubectl 1.37.1 (active) and 1.35.3. helm is installed under the AIDC data directory; the path is in the result.
Check health
Is the toolchain healthy?
A build fails in a way that looks like a missing tool, and you want to rule out the toolchain before digging further.
Illustrative conversation
YouCheck that AIDC is healthy and can reach its hub.
Tool callaidc_query { "action": "doctor" }
What happensAIDC reports applicable diagnostics, including warnings or errors to review.
Tool callaidc_query { "action": "hub" }
What happensThe hub is enabled and the connection check reports connected.
AgentI will review these findings and query each required tool before treating the project as ready.
Set up a project
Set up a fresh checkout
You have copied a project to your machine. It lists the tools it needs, but none are installed yet.
Illustrative conversation
YouSet up the toolchain for this project.
Tool callaidc_install { "action": "project", "projectDir": "/workspace/example" }
What happensAIDC installs the declared tools and reports each one.
Tool callaidc_query { "action": "current", "projectDir": "/workspace/example" }
What happensAIDC reports the current selection.
Tool callaidc_query { "action": "list", "tool": "nodejs", "projectDir": "/workspace/example" }
What happensInstalled versions are reported for this required tool; repeat for each required tool.
AgentI will compare installed presence and current selection with the project declaration, then run each required tool's own version command in the project's shell.
Add and pin
Add a tool and pin its version
The project needs a newer Node.js than the one it uses today.
Illustrative conversation
YouInstall Node.js 22 and use it for this project.
Tool callaidc_install { "action": "tool", "tool": "nodejs", "version": "22", "projectDir": "/workspace/example" }
What happensAIDC installs Node.js 22.
Tool callaidc_activate { "tool": "nodejs", "version": "22", "scope": "project", "projectDir": "/workspace/example" }
What happensThe project's .aidc.yaml selects Node.js 22.
AgentNode.js 22 is installed and selected for this project.
Upgrade
Upgrade, after looking first
A tool has a newer version and you want to move to it without surprises.
Illustrative conversation
YouUpgrade Node.js, but show me what it would do first.
Tool callaidc_upgrade { "tool": "nodejs", "projectDir": "/workspace/example" }
What happensA preview: the resolved target version and what would be installed and activated. Nothing is changed.
AgentThis would move Node.js to the version shown in the preview. Should I apply it and keep the old version?
YouYes, keep the old one.
Tool callaidc_upgrade { "tool": "nodejs", "version": "EXACT_REVIEWED_VERSION", "keep": true, "apply": true, "projectDir": "/workspace/example" }
What happensAIDC attempts the reviewed exact version and keeps the previous installation; replace EXACT_REVIEWED_VERSION with the version you approved.
AgentNode.js is upgraded and the previous version is still installed in case you need it.
Clean up
Clean up old versions
Old tool versions pile up and you want the disk space back without breaking what a project still uses.
Illustrative conversation
YouRemove old tool versions I no longer use.
Tool callaidc_remove { "action": "prune", "projectDir": "/workspace/example" }
What happensA dry run: AIDC lists the versions it would remove and removes nothing.
AgentThese versions are unused by this project. Other projects may still need some of them. Do you want me to remove them?
YouGo ahead.
Tool callaidc_remove { "action": "prune", "confirm": true, "projectDir": "/workspace/example" }
What happensAIDC removes the listed versions.
AgentThe unused versions are removed. This project's versions were not touched.