feat(tui): add a provider slot to the footer status line - #2461
Open
hikariming wants to merge 1 commit into
Open
feat(tui): add a provider slot to the footer status line#2461hikariming wants to merge 1 commit into
hikariming wants to merge 1 commit into
Conversation
The footer showed the model name but never said which provider serves it, so look-alike model names across providers were indistinguishable. Add an opt-in `provider` status-line slot: list it in `[status_line].items` to render the provider ahead of (or anywhere around) the model name. The default layout is unchanged. The same value also ships in the `[status_line].command` JSON payload as `provider`. `providerDisplayName` moves from the model selector dialog to `tui/utils/provider-label.ts` so the footer can reuse it without chrome depending on dialogs; the `managed:` prefix stays hidden from the UI.
🦋 Changeset detectedLatest commit: db0e11d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
1 participant
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.
Related Issue
No prior issue; the problem is explained below.
Problem
The footer status line shows the current model name but never says which provider serves it. With several providers configured, look-alike model names (the same open-weights model offered by different providers, or similarly named aliases) are indistinguishable in the footer — you cannot tell who is actually serving the request without opening the model selector.
What changed
providerslot to the built-in status line. Listingproviderin[status_line].items(tui.toml) renders the provider label next to the model name; the id is accepted anywhere in the order, like the other slots. The default layout is unchanged — the slot only appears when explicitly listed.[status_line].commandJSON payload now carries the same value as aproviderfield, so custom status line scripts can use it too.providerDisplayNamemoved from the model selector dialog totui/utils/provider-label.tsso the footer can reuse it without chrome depending on dialogs; themanaged:id prefix stays hidden from the UI as before.This follows the existing slot architecture of the footer:
provideris one more entry inSTATUS_LINE_ITEMSrendered through the same slot pipeline, so ordering, truncation, and the items-config validation all apply to it for free. Docs (en/zhconfig-files.md) are updated and unit tests cover the slot rendering, the opt-in default, the unknown-alias fallback, and the command payload field.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.