feat(tui): label context, cache, and generated tokens in the wide status line - #238
Merged
Max17190 merged 2 commits intoAug 27, 2026
Merged
Conversation
Max17190
marked this pull request as ready for review
August 27, 2026 03:53
Max17190
force-pushed
the
tui-statusline-cache-tokens
branch
from
August 27, 2026 03:55
3470359 to
c7dfb30
Compare
Max17190
force-pushed
the
tui-statusline-cache-tokens
branch
2 times, most recently
from
August 27, 2026 05:19
5750947 to
47e652b
Compare
…tus line Cache hit rate and generation volume existed only behind /context and /status, so the costs the harness treats as design stayed invisible while working. At 100 columns and up the status line now reads 'model ctx N% cache M% out 16.8k approvals': labeled, because two bare percents are indistinguishable. Generated tokens sum completion tokens only; prompt tokens are deliberately not summed, since every request resends the history and their sum would measure resending, not work. Narrower tiers keep their historical shapes.
The wide tier rendered the full model id and let the row clip whatever followed, so a long id ate ctx, cache, out, and the approval mode. The tail is built first and the model id is clipped to the width it leaves over; short ids keep the tier's historical shape byte for byte.
Max17190
force-pushed
the
tui-statusline-cache-tokens
branch
from
August 27, 2026 08:01
47e652b to
af28d94
Compare
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.
Why
Cache hit rate and generation volume exist only behind
/contextand/status, so the costs the harness treats as design stay invisible while working.Summary
At 100 columns and up the status line reads
model ctx N% cache M% out 16.8k approvals: labeled, because two bare percents are indistinguishable. Generated tokens sum completion tokens only; prompt tokens are deliberately not summed, since every request resends the history and their sum would measure resending, not work. Narrower tiers keep their historical shapes; the meter resets with/new.Test Plan
compact_counts_read_like_a_human_wrote_them(842 / 1k / 16.8k / 17k / 2.4M).wide_status_line_labels_context_cache_and_generated_tokens(labels, accumulation across usage reports, and the 78-column tier unchanged), shown red with the wide tier disabled.Greptile Summary
The wide TUI status line now shows labeled context, cache, and generated-token metrics while preserving the approval mode when model identifiers are unusually long. The generated-token meter counts completion output for the current app run and clears when a new session begins.
Confidence Score: 5/5
No blocking failure remains; the rendered wide status line retains its essential tail under a long model identifier.
No accepted blocking findings remain.
What T-Rex did
Reviews (4): Last reviewed commit: "fix(tui): the wide status tail survives ..." | Re-trigger Greptile