Skip to content

fix(chrome): persist composer model pick for new sessions - #18

Merged
Warexpor merged 1 commit into
mainfrom
cursor/persist-composer-model-4b81
Sep 4, 2026
Merged

fix(chrome): persist composer model pick for new sessions#18
Warexpor merged 1 commit into
mainfrom
cursor/persist-composer-model-4b81

Conversation

@Warexpor

@Warexpor Warexpor commented Sep 4, 2026

Copy link
Copy Markdown
Owner

What changed

onModelChange now calls saveLastModelChoice(harness, resolved.id), so switching model from the composer’s picker also updates the default new sessions start with.

Why

monocode.lastModel was written only by Settings → Providers. The composer picker updated just the current session (saveLastModelSettings still made effort sticky), so defaultSessionChoice() 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. saveLastModelChoice also writes the per-provider default, so Settings stays aligned.

UI

No visual change.

Checklist

  • I ran npm run check:web (1200 tests + tsc --noEmit)
  • This PR is small and focused
  • I did not mix unrelated changes
Open in Web Open in Cursor 

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
Warexpor marked this pull request as ready for review September 4, 2026 20:09
@Warexpor
Warexpor merged commit 061b24c into main Sep 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants