promptgarten ๐ŸŒฑ
๐ŸŒ ES

Command reference ยท Aider

/ask

Asks questions about the codebase without Aider changing any files.

In ask mode, Aider answers questions about the code but never changes files. The docs describe a common workflow of bouncing between /ask and /code: discuss the plan with /ask first, then trigger the actual change with /code. Without an attached prompt, /ask only switches to the mode persistently.

โœ… WHEN TO USE IT?

Discuss a plan before changing code

/ask What's the best way to add caching to this function? โ€” once you agree, switch to code mode and just say "go ahead"

Understand the codebase without accidentally changing it

/ask What does the retry logic in api_client.py do?

โ›” WHEN NOT TO?

Wanting an immediate code change

The docs say ask mode never makes changes to files.

Better: Use /code for the actual implementation

Asking about Aider itself (usage/configuration)

/ask is meant for questions about the codebase, not about Aider as a tool.

Better: Use /help for questions about Aider's usage, configuration, or troubleshooting

SOURCES