feat: Improve fallback provider selection with API key validation #779
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.
Fixes #777
Owner: @bracesproul
Changes
This PR implements a robust mechanism to filter fallback providers based on API key availability:
hasApiKeyForProvider()method toModelManagerto safely check API key configurationgetModelConfigs()to skip providers without valid API keysFallbackRunnableerror handling to provide clear feedback when no fallback providers are availableKey Improvements
Technical Details
Updated
/src/utils/llms/model-manager.tshasApiKeyForProvider()methodUpdated
/src/utils/runtime-fallback.tsTesting
Resolves the issue of indiscriminate provider fallback when API keys are not configured.