Setting to hide the permission-mode hint: it is not truncated in narrow panes while custom status lines are
Summary
In narrow split panes, the permission-mode hint below the status line costs
disproportionately more than in a full-width terminal, because the hint is
never truncated while the custom status line is.
Previous requests for this setting (#46419, #53268, #56956, #57957, #10406,
#17368) were all closed — several as duplicates of each other, the canonical
one as not planned after inactivity — and all are now locked. Filing fresh
per the auto-lock message, with a measurement the earlier reports did not have.
The asymmetry
Running three agents side by side in a terminal multiplexer, a 205-column
terminal gives each pane 68 columns. Measured at that width:
| Line | Width | Behaviour at 68 cols |
|---|---|---|
| Permission-mode hint | 51 chars, fixed | Renders in full |
| Custom status line | ~74 chars | Truncated to Model: Opus 5 \| ⎇ some-bra... |
So the line the user configured gets cut, and the line the user cannot
configure survives intact. At 120 columns the status line fits completely —
the problem is specific to narrow panes, which is exactly where vertical and
horizontal space are scarcest.
With three panes, that is three rows spent repeating a keybinding hint.
Why a custom status line makes it redundant
rate_limits and the rest of the payload already let a custom status line
surface whatever state matters. Users who write one have, by definition,
decided what belongs on that row. The built-in hint duplicates a keybinding
that becomes muscle memory within the first session.
Request
A settings.json flag to opt out, e.g.:
{ "statusLine": { "hidePermissionHint": true } }
Naming is not the point — any opt-out works. Verified on 2.1.252: nohide* key exists in the bundle today (grep -aoE '"hide[A-Za-z]{3,30}"'
returns nothing), so this is not a discoverability problem.
Alternatives considered
tui— enum is["default","fullscreen"], controls the renderer only.- Trimming status line widgets — recovers horizontal space, not the row, and
gives up information the user chose to display.
- Zooming the pane — works, but defeats the purpose of running agents in
parallel.