What it doesBasics
- Installed and available version discovery
- Install and activation operations
- Workspace setup
- Health and current-state reporting
First useBasics
- Query the selected project's tool state before requesting an installation change.
- Choose an explicit version operation.
- Verify the resulting environment before continuing work.
Everyday tasksEveryday use
Review and apply a project tool upgrade
An agent needs to update a project tool without applying an unreviewed change.
- Query tool state in the intended project directory.
- Request the upgrade without apply to obtain a preview.
- Review the proposed change, then repeat with apply enabled.
- Query current state to verify the selected version.
What you getThe approved upgrade is applied in the same project context that was inspected.
How to check: The preview, applied command result, exit status, and final current-version query.
Remove an obsolete installation deliberately
An installed version is no longer needed and removal must remain reviewable.
- Query installed versions.
- Request removal without confirmation to obtain the plan.
- Confirm the exact target, then repeat with confirmation.
- Query installed versions again.
What you getOnly the reviewed installation is removed.
How to check: The no-change plan, confirmed result, exit status, and post-removal inventory.
Settings to decideAdvanced
- AIDC executable
- Keep the default executable name when AIDC is on the server PATH; otherwise provide the reviewed executable path at server launch.
- Project directory
- Pass projectDir for project-sensitive work so each call targets the intended project.
- Activation scope
- Choose project, home, or session scope explicitly according to how widely the selection should apply.
- Mutation gates
- Keep upgrade apply and removal confirmation false during review; enable them only for the approved target.
- Server authority
- Run the server with least privilege and a bounded environment. Confirmation records caller intent, and child processes run with the server’s own identity and access.
CommandsAdvanced
$ aidc_query({"action":"doctor","projectDir":"/workspace/project"})
$ aidc_upgrade({"tool":"nodejs","projectDir":"/workspace/project","apply":false})
$ aidc_upgrade({"tool":"nodejs","projectDir":"/workspace/project","apply":true})
$ aidc_query({"action":"current","projectDir":"/workspace/project"})
Problems and fixesHelp
What you seeCheckFix
Queries or setup report tools for the wrong project.Inspect the projectDir sent with the request and confirm the project configuration exists there.Repeat the operation with the intended absolute project context, then query before mutating.
An upgrade or removal returns a plan but changes nothing.Check whether apply or confirm was deliberately left false.Review the plan and repeat with the appropriate gate enabled only after approval.
The result ends before the useful diagnostic detail.Inspect the truncated field and exit code.Narrow the query or reproduce the exact AIDC operation through an approved diagnostic path.
What you see
Queries or setup report tools for the wrong project.
Check
Inspect the projectDir sent with the request and confirm the project configuration exists there.
Fix
Repeat the operation with the intended absolute project context, then query before mutating.
What you see
An upgrade or removal returns a plan but changes nothing.
Check
Check whether apply or confirm was deliberately left false.
Fix
Review the plan and repeat with the appropriate gate enabled only after approval.
What you see
The result ends before the useful diagnostic detail.
Check
Inspect the truncated field and exit code.
Fix
Narrow the query or reproduce the exact AIDC operation through an approved diagnostic path.
Good to knowHelp
- Child operations run with the server process identity, environment and filesystem access.
- Set projectDir on project-sensitive calls to target the intended project.
- Mutating calls require explicit intent, and output is bounded to a documented size.