Repository navigation
feat(statusline): name the model a routing choice served beside the session's own - #507
Merged
Merged
Conversation
…ession's own
A session whose model something else picks for it (a virtual model's mode,
an antigravity tier alias) showed only the name it typed, so what was
actually serving was invisible where the person looks. The door now records
the choice on the usage record: the name the session asked for, and the
distinct providers the choice could have landed on. The statusline draws it
as "auto -> glm-5.3", folding the provider in ("auto -> z/glm-5.3") when
the choice could cross providers or left the launch's own, replacing the
separate via segment in that case.
The antigravity relay also names the model that served in message_start
instead of echoing the alias, so a usage record attributes quota to the
backend model rather than the tier name.
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.
feat(statusline): name the model a routing choice served beside the session's own
A session whose model something else picks for it (a virtual model's mode,
an antigravity tier alias) showed only the name it typed, so what was
actually serving was invisible where the person looks. The door now records
the choice on the usage record: the name the session asked for, and the
distinct providers the choice could have landed on. The statusline draws it
as "auto -> glm-5.3", folding the provider in ("auto -> z/glm-5.3") when
the choice could cross providers or left the launch's own, replacing the
separate via segment in that case.
The antigravity relay also names the model that served in message_start
instead of echoing the alias, so a usage record attributes quota to the
backend model rather than the tier name.