BC Observatoryunofficial, made by waldo
community postAL Developmentcommunity - not Microsoftreviewed - checked by Opus

AL Development with Claude Code: A Multi-Agent Workflow

AL development with Claude Code works best using a multi-agent workflow where specialized agents handle planning, development, code review, testing, and diagnostics sequentially. This approach keeps context manageable by writing results to files and reading only relevant documents, enabling extended development cycles and consistent output quality.

Open in Claudehttps-stefanmaron-com-posts-al-development-claude-code-multi-agent-workflow--a7e0cfef9c.md

post Stefan Maron

Stefan Maron · 2026-01-28 · 1,252 words · about 6 min

"AL is niche enough that LLMs struggle without guidance, and large refactoring tasks blow up the context window within a few agent calls."
Show the post hereRead on Stefan Maron

Key points

  • Sub-agents write their results to files and return only a one-line summary, which keeps the main session’s context small and lets work resume later
  • The /plan, /develop and /test commands run agents in sequence, with approval gates between the planning steps
  • The al-compile tool from al-smart-compile finds the AL compiler, the analyzers and the package cache on its own; a diagnostics agent uses it to fix issues until the build is clean
  • A code-review agent working in a fresh context found issues such as DRY violations before the author reviewed the code
  • In the demo, about an hour of unattended refactoring touched 42 files and compiled with no errors

Quotes

  • “AL is niche enough that LLMs struggle without guidance, and large refactoring tasks blow up the context window within a few agent calls.” (Explains the core problem that multi-agent workflows solve for AL development)
  • “My AL knowledge and experience with BC is worth more when I’m directing and reviewing than when I’m physically typing the code.” (Expresses the philosophical shift from hands-on coding to strategic direction in AI-assisted development)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

  • other “profile-al-development”
  • other “al-compile”
  • other “al-smart-compile”

Context

  • Features: sub-agent workflow, plugin system, document-driven development, requirements engineering, solution planning, code review automation, diagnostic fixing, test planning
  • Versions: BC v18+

Source: Stefan Maron, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.