Gemini 2.5 Pro needs weak model assignment #3711 #4566
+212
−238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This GitHub issue (#3711) for the Aider project addresses a problem with the gemini/gemini-2.5-pro model. It notes that the powerful model, which has tight rate limits, was being unnecessarily used for simple commit messages. The solution proposed and implemented in model-settings.yml is to assign a lighter, faster model like gemini-1.5-flash as the weak_model_name. This preserves the primary model's quota for complex coding tasks.