Tips

Just add the files that need to be changed to the chat

Take a moment and think about which files will need to be changed. Aider can often figure out which files to edit all by itself, but the most efficient approach is for you to add the files to the chat.

Don’t add lots of files to the chat

Just add the files you think need to be edited. Too much irrelevant code will distract and confuse the LLM. Aider uses a map of your entire git repo so is usually aware of relevant classes/functions/methods elsewhere in your code base. It’s ok to add 1-2 highly relevant files that don’t need to be edited, but be selective.

Break your goal down into bite sized steps

Do them one at a time. Adjust the files added to the chat as you go: /drop files that don’t need any more changes, /add files that need changes for the next step.

For complex changes, discuss a plan first

Use the /ask command to make a plan with aider. Once you are happy with the approach, just say “go ahead” without the /ask prefix.

If aider gets stuck

  • Use /clear to discard the chat history and make a fresh start.
  • Can you /drop any extra files?
  • Use /ask to discuss a plan before aider starts editing code.
  • Use the /model command to switch to a different model and try again. Switching between GPT-4o and Sonnet will often get past problems.
  • If aider is hopelessly stuck, just code the next step yourself and try having aider code some more after that. Take turns and pair program with aider.

Creating new files

If you want aider to create a new file, add it to the repository first with /add <file>. This way aider knows this file exists and will write to it. Otherwise, aider might write the changes to an existing file. This can happen even if you ask for a new file, as LLMs tend to focus a lot on the existing information in their contexts.

Fixing bugs and errors

If your code is throwing an error, use the /run command to share the error output with the aider. Or just paste the errors into the chat. Let the aider figure out how to fix the bug.

If test are failing, use the /test command to run tests and share the error output with the aider.

Providing docs

LLMs know about a lot of standard tools and libraries, but may get some of the fine details wrong about API versions and function arguments.

You can provide up-to-date documentation in a few ways:

  • Paste doc snippets into the chat.
  • Include a URL to docs in your chat message and aider will scrape and read it. For example: Add a submit button like this https://ui.shadcn.com/docs/components/button.
  • Use the /read command to read doc files into the chat from anywhere on your filesystem.
  • If you have coding conventions or standing instructions you want aider to follow, consider using a conventions file.

Interrupting & inputting

Use Control-C to interrupt aider if it isn’t providing a useful response. The partial response remains in the conversation, so you can refer to it when you reply with more information or direction.

You can send long, multi-line messages in the chat in a few ways:

  • Paste a multi-line message directly into the chat.
  • Enter { alone on the first line to start a multiline message and } alone on the last line to end it.
  • Enter {tag (where “tag” is any sequence of letters/numbers) and end with tag}. This is useful when you need to include closing braces } in your message.
  • Use Meta-ENTER to start a new line without sending the message (Esc+ENTER in some environments).
  • Use /paste to paste text from the clipboard into the chat.
  • Use the /editor command to open your editor to create the next chat message.

Example with a tag:

{python
def hello():
    print("Hello}")  # Note: contains a brace
python}