Repository navigation
fix: show newest provider models first in Desktop and Web UI - #229
Open
KillerQueen-Z wants to merge 1 commit into
Open
KillerQueen-Z wants to merge 1 commit into
KillerQueen-Z wants to merge 1 commit into
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
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.
The Desktop/browser model dropdown currently sorts model labels alphabetically within a provider, putting older Gemini, GPT and Claude generations before newer ones. Build the
models.listresponse with Model Core's shared newest-first helper and reuse it in the expanded terminal picker. Available chat models remain grouped by company; free flags, labels, shortcuts, context sizes and live prices are preserved.Depends on model-catalog #7. The package and lockfile pin the exact Model Core commit
a9d7dd21e65c744104dd752a13d7bf5a71e27f01, making the helper available without waiting for an npm publication.Release dates take precedence when a provider group has complete verified date coverage. The current gateways supply a shared placeholder
createdtimestamp rather than release dates, so current lists use descending numeric generations (Gemini 4 before 3.8 before 3.1; GPT 6.1 before 6 before 5.x). Same-generation ties preserve source order. Remove the terminal picker's separate weighted version/tier scores so both full pickers follow the same rule.Validation:
npm run buildpasses with the pinned catalog archive.buildModelList: all 85/85 Base and 82/82 Solana available chat models are retained, including uncurated models. Gemini 4 Argon and GPT 6.1 Sol lead their respective provider groups.This PR needs to be merged and included in a Franklin release before installed apps receive the change.