Repository navigation
agent_ui: Save configuration defaults after acceptance - #65849
Merged
Merged
Conversation
benbrandt
marked this pull request as ready for review
October 19, 2026 20:37
This was referenced Oct 19, 2026
bennetbo
approved these changes
Oct 20, 2026
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.
Save agent configuration defaults only after a successful request, using the value in the authoritative response rather than the requested value.
Cycling, boolean switches and picker confirmation previously wrote the requested default before sending the RPC. Rejection or a normalized response could therefore leave incorrect preferences for future sessions. All three controls now share one response-handling path:
Release Notes: