Don't use gpt 4.1 as hardcoded fallback #2446
Merged
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR removes the hardcoded fallback to the 'gpt-4.1' model when selecting a default chat endpoint. Instead of using await this._endpointProvider.getChatEndpoint('gpt-4.1') as a fallback, the code now dynamically finds the first endpoint with showInModelPicker enabled, making the model selection more flexible and avoiding dependencies on specific model names.
Key changes:
- Replaced hardcoded 'gpt-4.1' fallback with dynamic selection based on
showInModelPickerproperty - Improved fallback chain to be: CAPI default → first model picker-enabled endpoint → first available endpoint
rzhao271
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.