feat: add model-specific thinking defaults and custom model rows#10
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
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.
This PR introduces a centralized built-in Gemini model catalog (labels, allowed thinking levels, and defaults) and extends settings normalization with
modelThinkingLevelMap. The options page now manages per-model thinking defaults for Flash/Pro and supports add/remove rows for multiple custom models with per-model thinking levels. The chatpanel composer now resolves model labels and thinking choices from shared settings metadata and updates custom models/defaults live from storage while preserving explicit user-selected thinking levels. Unit tests were expanded across shared settings, options DOM/form/bootstrap, and chatpanel input-toolbar flows to cover the new behavior and regressions.