feat(llm, cli): Improve error message for unknown models#211
Merged
Conversation
When a user specified a model that did not exist for a provider, the application would return a generic and unhelpful API error. This made it difficult for the user to understand what went wrong and how to fix it. This change introduces specific error handling for this scenario. The Gemini provider logic now inspects 404 errors to detect when an unknown model is the cause. The CLI now catches this new `UnknownModel` error and enhances it by fetching the list of available models from the provider, presenting a much more user-friendly and actionable error message to the user. Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When a user specified a model that did not exist for a provider, the application would return a generic and unhelpful API error. This made it difficult for the user to understand what went wrong and how to fix it.
This change introduces specific error handling for this scenario. The Gemini provider logic now inspects 404 errors to detect when an unknown model is the cause.
The CLI now catches this new
UnknownModelerror and enhances it by fetching the list of available models from the provider, presenting a much more user-friendly and actionable error message to the user.