feat(cli): responsive priority-based status line for narrow terminals (#3421) - #3423
Open
me2seeks wants to merge 1 commit into
Open
feat(cli): responsive priority-based status line for narrow terminals (#3421)#3423me2seeks wants to merge 1 commit into
me2seeks wants to merge 1 commit into
Conversation
…apache#3421) The status line joined every segment left-to-right and hard-truncated the right side on overflow, cutting whichever segment happened to sit at the boundary mid-token and treating low-value static segments (connection, cwd) the same as safety- and budget-relevant ones. Segments now carry a drop rank; on overflow whole segments drop lowest-value-first (cache, cost, connection, thinking, orchestration), cwd degrades full -> basename -> dropped, and title/permission mode/goal/ctx never drop. Wide rendering is unchanged; the previous hard truncation remains only as the final fallback.
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.
Closes #3421
Problem
At ≤100 cols the status line hard-truncated the right side mid-token (
cache 6…), treating low-value static segments (connection, cwd) the same as safety/budget-relevant ones. A typical session already overflows 80 cols (~84 chars with no usage segments; ~122 with ctx/cost/cache and a long model id).Change
renderMakaPiStatusLinenow assembles segments with drop ranks and degrades responsively:cache %→$cost→ connection slug →thinking:→swarm/graph→ cwd → (final fallback: existingfitLinetruncation)~/full/path→ basename → droppedcache 40%now uses a 120-col terminal (at the default 80 the segment is correctly dropped)No new configuration surface. Whether user-facing segment configuration is wanted on top of this is raised as an open question on the issue; it can land independently later.
Tests