Aider
Aider errors and fixes
17 Aider error messages, quoted verbatim, each with what it means, why it happens and the fix documented in official docs, maintainer replies or release notes. Verified .
All Aider errors
- Status: Fixed in release2 fixed in release
- Status: Workaround8 workaround
- Status: By design6 by design
- Status: Open1 open
The LLM did not conform to the edit format.The model replied with code changes in a format aider could not parse or apply, so the edits were not written to your files. The docs also describe this as aider saying something like "Failed to apply edit to *filename*". Aider prints a link to the edit-errors doc and sends the parse error back to the model so it can retry.Status: WorkaroundSearchReplaceNoExactMatch: This SEARCH block failed to exactly match lines in {path}In the diff (SEARCH/REPLACE) edit format, the SEARCH section the model sent does not match the current contents of the file, so that block was not applied. Aider's message says: "The SEARCH section must exactly match an existing block of lines including all white space, comments, indentation, docstrings, etc". It may add "Did you mean to match some of these actual lines from {path}?" or "Are you sure you need this SEARCH/REPLACE block? The REPLACE lines are already in {path}!". This is a form of the edit-format failure, and aider sends the message back to the model so it can resend only the failed blocks.Status: WorkaroundModel gpt-3.5-turbo has hit a token limit!The API provider reported that the request went over the model's context window (input plus output) or its output token limit. Aider reports the error and suggests actions. The token counts it prints are estimates. Aider never enforces token limits; it only reports token limit errors from the API provider. Lines such as "-- exceeded output limit!" or "-- possibly exhausted context window!" show which limit was hit.Status: WorkaroundModel foobar: Unknown context window size and costs, using sane defaults.Aider does not recognize the model name, so it does not know the context window size or token costs. It falls back to an unlimited context window and assumes the model is free. The docs say this is usually not a significant problem and you can probably ignore it. When the name looks like a typo, aider adds "Did you mean one of these?" with similar model names.Status: By designModel azure/gpt-4-turbo: Missing these environment variables:The model you picked needs provider environment variables that are not set, for example AZURE_API_BASE, AZURE_API_VERSION and AZURE_API_KEY for azure/ models. If you start chatting anyway, you will get errors.Status: By designaider: The term 'aider' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.The aider command is not on your shell PATH, so the shell cannot find it.Status: Workaroundaider-chat 0.23.0 requires somepackage==X.Y.Z, but you have somepackage U.W.V which is incompatible.Aider is installed with the wrong versions of its dependencies. This shows up as pip conflict messages like the one above, or as ImportErrors when aider runs. Aider pins its dependencies and is tested with those exact versions.Status: WorkaroundThe API provider is not able to authenticate you. Check your API key.The provider returned a litellm AuthenticationError. Aider prints this description, treats the error as non-retryable, and stops the request.Status: By designThe API provider has rate limited you. Try again later or check your quotas.The provider returned a litellm RateLimitError. Aider treats this as retryable: it prints the raw error, this description, and "Retrying in N seconds...", doubling the delay each time. It gives up once the delay goes past RETRY_TIMEOUT (60 seconds).Status: By designThe API provider's servers are down or overloaded.The provider returned an InternalServerError, ServiceUnavailableError or BadGatewayError. Aider maps all three to this message and retries automatically with exponential backoff.Status: By designThe API provider timed out without returning a response. They may be down or overloaded.The request to the model API timed out before a response came back. Older versions showed raw errors such as "Request timed out: HTTPConnectionPool(host='localhost', port=1234): Read timed out. (read timeout=600)", which is common with slow local models (issue #276).Status: Fixed in releaseYou need to: pip install boto3You picked an AWS Bedrock model, but the boto3 package is not installed in aider's Python environment. Aider detects "boto3" in the litellm APIConnectionError and stops without retrying.Status: WorkaroundInsufficient credits with the API provider. Please add credits.The provider returned an APIError containing "insufficient credits" with code 402. Since v0.81.0 aider no longer retries this error.Status: By designEmpty response received from LLM. Check your provider account?The model API returned no content for the request. Aider shows this warning and suggests checking your provider account.Status: OpenAider only works with git repos with version number 1 or 2.Your git repo uses an index format that GitPython, which aider uses, cannot read, usually index version 3 or later. Older versions crashed with an AssertionError traceback through index.entries (issue #211). Current versions catch this at startup and print this message, followed by "You may be able to convert your repo: git update-index --index-version=2".Status: WorkaroundException: Application is not running. Application.exit() failed.With --watch-files, the file-watcher thread crashed while trying to interrupt the input prompt. In issue #2716 the reporter traced it to TERM=dumb, for example when running aider inside an Emacs interface. The maintainer explained that watching for file changes needs to be able to interrupt the input prompt.Status: Fixed in releaseOllamaError: Error getting model info for ollama/qwen2.5-coder:32b. Set Ollama API Base via `OLLAMA_API_BASE` environment variable. Error: [Errno 61] Connection refusedAider could not reach your Ollama server to fetch model info. The maintainer said aider used to swallow this Ollama exception, which showed up only as an "Unknown context window size" warning, and changed it to surface the error.Status: Workaround
New to Aider? Start with Aider in the tools directory.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.