Repository navigation
V2 TUI: simplify provider labels in prompt and model picker #36270
Description
Summary
Make provider labeling in the V2 TUI more concise while preserving the distinction between Anomaly subscriptions and BYOK providers.
Proposed display
In the prompt, use the concise account/provider label:
Build · GPT-5.6 Sol · Anomaly · xhigh
Instead of the current verbose form:
Build · GPT-5.6 Sol · anomaly (OpenAI) · xhigh
In the model picker, keep the backing provider visible when it is needed to distinguish sources:
Anomaly (OpenAI)
GPT-5.6 Sol
Anomaly (OpenCode)
Mimo 2.5
When the user has no BYOK providers configured, collapse this further:
Anomaly
GPT-5.6 Sol
Mimo 2.5
Expected behavior
- The prompt uses the shortest useful provider/account name.
- The model picker preserves enough provider detail to distinguish Anomaly subscriptions from BYOK models.
- Without BYOK providers, Anomaly-hosted models appear in one concise group.
Activity
kitlangton commentedon Jul 11, 2026
Implementation note: the V2 TUI currently receives each model’s
providerIDand the available provider list, but subscription models do not expose their backing provider as structured metadata. For example, the TUI can tell that GPT-5.6 Sol comes throughopencode, but not that its backing provider is OpenAI.This means we can shorten the prompt label to
Anomalyand detect whether any BYOK provider is configured, but we cannot reliably renderAnomaly (OpenAI)only when OpenAI overlaps. Inferring this from model names or IDs would be brittle. The picker behavior therefore needs a backing-provider field (for example,upstreamProviderID) added to the model/catalog contract, or another explicit source of that relationship, before implementing overlap-based grouping.It may be useful to treat this as two parts: the immediately available prompt-label simplification, and the picker grouping once that metadata contract is defined.