feat: unify CLI and TUI provider cards - #6360
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.
Summary
Matching CLI/TUI providers now appear as one AI Providers card with shared enablement and model catalogs, explicit CLI/TUI system-default buttons, mode-specific editors, and a Shell link that always launches TUI. Direct API connections and differently configured backends retain separate cards.
An input-gated migration enables both modes when either was enabled and unions their catalogs. Both execution IDs remain available to model selectors and saved tasks; existing arguments, mode defaults, consent, and the active mode survive upgrades. Catalog updates that deliberately repick defaults also repair a removed sibling default. Broader harness/backend connection design is tracked in #6359.
Test plan