Repository navigation
Allow a temporary model choice for the next conversation turn - #708
Merged
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
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.
Change
The composer’s ellipsis menu now offers a model for the next turn. A visible notice and cancel button show the temporary choice even when the menu is closed. Sending or queueing the message consumes that choice; subsequent turns retain the existing default and its parameters. Queued requests preserve their submitted model when later executed.
Uses the existing provider catalogues and request-level model fields, with no new backend policy or persistent preference writes.
Validation
Browser validation used a local catalogue fixture, without authenticated generation or provider calls. Evidence retained in the task worktree under
.run/turn-model-evidence/and.run/turn-model-browser/.Task: #V#task_agent_25ffdc946001037728f20e865503457a. Tier 1. Merge decision: ready; temporary state, single-turn request binding, restoration and queue preservation verified. No deployment requested.