Repository navigation
Conversation
Assistant message footers name the model but not the variant it ran with, so a turn on high reasoning effort reads the same as one on the default. The variant is stored on every message and the prompt shows the current one, but nothing shows which one a past turn used. footer_variant in tui.json (default false) adds the message's variant, e.g. high or max, after the model in assistant message footers. Turns without a variant are unchanged. Documented in tui.mdx.
Contributor
|
The following comment was made by an LLM, it may be inaccurate: |
Contributor
|
Thanks for putting this together, @Nowaker, and for the clear write-up and testing notes! v1 (the Showing each turn's variant in the footer still makes sense for v2. You're welcome to open it against the |
This was referenced Oct 8, 2026
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.
Note: I'm aware v1 is now the maintenance branch and new features go to v2 only. This PR is here for others who want to use it on v1. I will submit a v2 version once I've migrated my plugin setup to v2.
Issue for this PR
Closes #53846
Type of change
What does this PR do?
Adds
footer_varianttotui.json, so you can see which variant, such as the reasoning effort, each assistant turn ran with. Without it, a turn onhighand a turn on the default read the same once you have switched.false(default): footers unchanged.true: the variant stored on the message follows the model in every assistant message footer, e.g.▣ Build · Claude Opus 4.5 · high · 45.5s. Turns that ran without a variant are unchanged.The footer reads
message.variant, so a past turn keeps the variant it ran with after the selection changes. The prompt line already shows the current variant and is not touched. Documented intui.mdx.Independent of other open PRs: it applies to
devon its own. If #53639 (model_label) or #53195 (turn timing) also land, the variant sits right after the model in those footers too, before any time and duration.How did you verify your code works?
test/config.test.tsxcovers decoding.bun typecheckandbun testpass inpackages/tui.XDG_*dirs on a throwaway tmux socket, OpenAI-compatible fake providers. Turn one runs without a variant, turn two onhigh; footers and the prompt line as captured:Checklist
This PR is AI generated, but under direct supervision and on request of @Nowaker.