Chat, Ask, or Edit? Using GitHub Copilot Effectively in AL Development
GitHub Copilot in Visual Studio Code offers three distinct modes for AL development - Chat for designing solutions, Ask for understanding and reviewing code, and Edit for refactoring - each serving different purposes and stages of development rather than being interchangeable.

post think about IT
"A frequent mistake is using Chat for everything. Chat can explain code. It can refactor code. That does not mean it should."
Key points
- Chat mode is best for high-level solution design and architectural decisions before writing code
- Ask mode functions as a code review assistant, explaining existing code and identifying issues without making changes
- Edit mode precisely refactors selected code blocks with focused improvements while preserving context
- Using the wrong mode causes Copilot to feel unreliable; intentional mode selection improves predictability and effectiveness
- Copilot Agent deserves separate consideration as it works across multiple files and objects differently than the three local modes
Quotes
- “A frequent mistake is using Chat for everything. Chat can explain code. It can refactor code. That does not mean it should.” (Highlights the core misconception that causes frustration with Copilot and explains why mode selection is critical for effectiveness.)
- “They support different phases of development: Chat helps you think, Ask helps you understand, Edit helps you improve.” (Reinforces that the three modes are complementary tools for different development phases rather than interchangeable alternatives.)
Context
- Features: Copilot Chat, Copilot Ask, Copilot Edit, code refactoring, solution design, code review, AL validation
Source: think about IT - Steven Renders, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.