Choose your environment. Start with ALDC.
One development approach. Instructions for the tool you use. Choose your surface, prepare your project, and ask your first bounded question.
Your tools. Your decisions.
Choose the delivery for your surface. The VS Code extension is available as 5.0.4 from the Marketplace. The reproducible source-based examples below remain pinned to v5.0.0. For current source and plugin deliveries, including Claude Code's own maintained evolution, consult the versions by channel.
Prepare the 5.0.0 source
For Claude Code, Copilot CLI and Codex: Git, Node.js 20+ and an installed, authenticated host. Use a separate AL project with app.json. Run these PowerShell commands from a tools folder outside that project, once. Choose a new ALDC-5.0.0 folder; do not overwrite an existing clone.
git clone https://github.com/javiarmesto/ALDC-AL-Development-Collection.git ALDC-5.0.0
if ($LASTEXITCODE -ne 0) { throw "Clone failed" }
git -C .\ALDC-5.0.0 checkout v5.0.0
if ($LASTEXITCODE -ne 0) { throw "Checkout failed" }
$aldc = (Resolve-Path .\ALDC-5.0.0).Path
$project = (Resolve-Path 'C:\Path\To\YourALProject').PathReplace the example project path before running. Keep this PowerShell session open: the following commands use $aldc and $project. The checkout is detached intentionally.
Inspect the 5.0.0 source · v5.0.0GitHub Copilot VS Code
Marketplace · 5.0.4Install the extension
You need VS Code, GitHub Copilot access and an AL project. Install from the official listing; this command installs the published channel.
code --install-extension javierarmestogonzalez.al-development-collectionOpen Marketplace · For VS Code Insiders, use code-insiders instead of code.
Install the toolkit in your AL project
Open the project folder containing app.json. From the Command Palette run AL Collection: Open Project Manager, choose the profile, preview the file list and confirm; the panel also verifies, restores and runs Doctor. AL Collection: Install Toolkit to Workspace does the same from the palette. Reload the window afterwards. Installing the extension alone does not populate the project.
Check discovery before implementation
The ALDC Visor view in the Explorer lists the plan artifacts of each requirement as they are created. Inspect the agent selector and choose AL Architecture & Design Specialist. Ask it to identify the instructions it actually loaded. Use that context to start a bounded design request.
Updating an existing project to 5.0.4?
Update the extension, run AL Collection: Update Toolkit, review the preview and managed-file collisions, then run AL Collection: Verify Installed Toolkit and reload the window. Updating the extension alone does not replace toolkit files in a project.
Installing from a VSIX file?
Use Extensions: Install from VSIX with the file, reload, then update the project toolkit. Review conflicts before replacing anything. BC28 is the default; bc29-native is optional.
GitHub Copilot CLI
Source · 5.0.0Preview the project setup
After preparing the source above, inspect the proposed file changes. This first command is a preview. Stop if you see an unexpected destination or collision.
node "$aldc/copilot-cli-plugin/scripts/init.js" --project "$project"Apply the reviewed changes
node "$aldc/copilot-cli-plugin/scripts/init.js" --project "$project" --applyUnrecognized or customized files remain visible conflicts. Do not add --force to bypass them without reviewing the replacement and backup. Project initialization and host plugin loading are separate steps.
Load ALDC in the host
copilot plugin install "$aldc/copilot-cli-plugin"
copilot plugin list
Set-Location -LiteralPath $project
copilotStart a fresh CLI session and inspect /agent and /skills list. Install aldc-cli, not both aldc and aldc-cli in the same session. Local plugin updates may require reinstalling the cached plugin.
Verify the installed files
node "$aldc/copilot-cli-plugin/scripts/init.js" --project "$project" --verifyA matching receipt verifies managed files. It does not verify skill loading, delegated agents, compilation or Business Central access.
Claude Code Plugin
Source · 5.0.0Preview the project setup
After preparing the source above, inspect the proposed file changes. This first command is a preview. Stop if you see an unexpected destination or collision.
node "$aldc/claude-plugin/scripts/init.js" --project "$project"Apply the reviewed changes
node "$aldc/claude-plugin/scripts/init.js" --project "$project" --applyUnrecognized or customized files remain visible conflicts. Do not add --force to bypass them without reviewing the replacement and backup. Project initialization and host plugin loading are separate steps.
Load ALDC in the host
Set-Location -LiteralPath $project
claude --plugin-dir "$aldc/claude-plugin"This loads the checked-out plugin for this session. Inspect /agents and the /aldc: commands. Avoid loading a second cached ALDC plugin at the same time. The local route does not require a Marketplace publication.
Verify the installed files
node "$aldc/claude-plugin/scripts/init.js" --project "$project" --verifyA matching receipt verifies managed files. It does not verify skill loading, delegated agents, compilation or Business Central access.
Codex Project setup
Source · 5.0.0Preview the project setup
After preparing the source above, inspect the proposed file changes. This first command is a preview. Stop if you see an unexpected destination or collision.
node "$aldc/plugins/aldc-codex/scripts/init.js" --project "$project"Apply the reviewed changes
node "$aldc/plugins/aldc-codex/scripts/init.js" --project "$project" --applyUnrecognized or customized files remain visible conflicts. Do not add --force to bypass them without reviewing the replacement and backup. Project initialization and host plugin loading are separate steps.
Load ALDC in the host
The bootstrap installs one local ALDC skill, project agent profiles and managed guidance. Open the project in Codex, start a fresh session and inspect the available ALDC skill and instruction sources. This is a project-local route; it does not register a plugin in a public marketplace.
Already using the ALDC Codex plugin? Use either plugin discovery or this local bootstrap in a project, never both. Plugin discovery alone does not install project agent profiles; see the distribution guide before changing routes.
Verify the installed files
node "$aldc/plugins/aldc-codex/scripts/init.js" --project "$project" --verifyA matching receipt verifies managed files. It does not verify skill loading, delegated agents, compilation or Business Central access.
Start with one design decision.
In the selected host, ask the ALDC Architect to work on a bounded requirement. First verify which instructions are available.
Use the ALDC Architect role. Identify the ALDC instructions and skills you actually loaded, or state what is missing.
Requirement: add an internal note to items so a user can consult it on the Item Card.
Read the target version from app.json. Assess the scope and propose the necessary specifications and dependencies. Do not generate AL, compile, deploy or change configuration. Stop for my review.What installation does not do
BC28 / BC29 profiles guide ALDC; they do not install the AL extension, compiler, symbols or a Business Central environment. Terminal hosts use their own available tools; VS Code tools are not portable by name. Configure each project for its target.
BCQuality is optional and separate. Doctor requires Python 3.9+ and reports configuration and observations per operation. Installing files is not a successful review or a compile pass.