fix(chrome): persist composer model pick for new sessions - #18
Merged
Conversation
The composer picker only updated the current session. monocode.lastModel was written solely by Settings → Providers, so defaultSessionChoice() kept falling back to the built-in default. Persist the pick via saveLastModelChoice, matching the effort chips and Settings. Co-authored-by: Warexpor <warexpor@gmail.com>
Warexpor
marked this pull request as ready for review
September 4, 2026 20:09
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.
What changed
onModelChangenow callssaveLastModelChoice(harness, resolved.id), so switching model from the composer’s picker also updates the default new sessions start with.Why
monocode.lastModelwas written only by Settings → Providers. The composer picker updated just the current session (saveLastModelSettingsstill made effort sticky), sodefaultSessionChoice()kept a stale or absent pick and new sessions fell back to the built-in default.This matches the intent of Settings → Providers and upstream hardbeat920#30 / PR hardbeat920#33.
saveLastModelChoicealso writes the per-provider default, so Settings stays aligned.UI
No visual change.
Checklist
npm run check:web(1200 tests +tsc --noEmit)