feat(chat): switch execution mode from the model picker#183
Merged
su-fen merged 3 commits intoJul 21, 2026
Conversation
The Chat/Agent execution mode lived only in Settings, several clicks away. Embed a compact mode segment at the top of the model dropdown on both the desktop ChatHeader and the WebUI fork: Chat | Agent side by side with the active mode highlighted, plus a hint that a switch applies from the next message while the conversation continues. Selecting a mode calls updateSystem on the global setting (idempotent when re-selecting the current mode); the panel stays open so users can adjust model and mode together. agent-dev counts as Agent: the segment shows "Agent·dev" and re-selecting Agent never downgrades it — the dev toggle remains settings-only. The model picker is the natural home because model and mode answer the same question (how the next reply is produced) and the dropdown costs no space on the crowded mobile composer. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Base UI migration moved the model picker's enter/exit from keyframe animations to transitions, but the prefers-reduced-motion block only disabled animations. Mirror the desktop CSS by adding .model-selector-dropdown to the transition: none group.
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
2 participants
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.
The Chat/Agent execution mode lived only in Settings, several clicks away. Embed a compact mode segment at the top of the model dropdown on both the desktop ChatHeader and the WebUI fork: Chat | Agent side by side with the active mode highlighted, plus a hint that a switch applies from the next message while the conversation continues.
Selecting a mode calls updateSystem on the global setting (idempotent when re-selecting the current mode); the panel stays open so users can adjust model and mode together. agent-dev counts as Agent: the segment shows "Agent·dev" and re-selecting Agent never downgrades it — the dev toggle remains settings-only. The model picker is the natural home because model and mode answer the same question (how the next reply is produced) and the dropdown costs no space on the crowded mobile composer.