Ask Mode
Discussion mode: Aider discusses the code and answers questions, but never changes files.
In ask mode, Aider answers questions about the codebase and discusses approaches, but makes no file changes. Recommended workflow: discuss options in /ask first and agree on a plan, then trigger the actual implementation with /code (often a short 'go ahead' is enough). Switch permanently with /chat-mode ask or /ask (no prompt), or for a single message with /ask <question>. Startup flag: --chat-mode ask.
โ WHEN TO USE IT?
Understand how part of the codebase works before changing anything
/ask How is authentication structured in this project?
Weigh multiple solution options before touching files
/ask What would be two sensible approaches to add rate limiting? โ then have the chosen approach implemented with /code
โ WHEN NOT TO?
The plan is already set, it should be implemented directly
In ask mode Aider never changes files as a matter of principle, even if the request sounds like an implementation order.
Better: Use /code, or switch to code mode
You want Aider to explain its own usage/configuration, not the project
/ask refers to the loaded project codebase, not to Aider itself.
Better: Use /help for questions about Aider's usage, configuration, and troubleshooting
SOURCES
- Aider Docs โ Chat Modes โ aider.chat