You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Statusline providers: support an explicit line break or vertical layout in the UI tree #62959
A way for a statusline provider (tui_extensions_statusline) to put content on a specific line, for example a column element, a break element, or rendering \n in text as a line break.
Shell-based status lines in other CLIs commonly use a fixed two-line layout (identity on line 1: model, project, branch; meters on line 2: context, rate limits, cost). The Codex UI tree only has row with wrap: "nowrap" | "wrap", so a provider cannot choose where a line ends. The footer can already span several lines when a wrapping row runs out of width, but where it breaks depends on the terminal width.
Possible shapes:
{ "type": "column", props: { gap }, children: [...] }, where each child is a line
{ "type": "break" } inside a row
row prop wrap: "always", which ends the line after this row
Any of these would let providers offer a stable multi-line layout. They would still stay within the existing node/size limits.
Additional information
What I tried: two groups of items, each in its own row, inside an outer row with wrap: "wrap":
Approach
Result
Bare "\n" string child between the rows
Newline dropped, rows run together
text element containing "\n"
Same
Each line in its own nested wrapping row
Single line while it fits
Trailing spaces to fill the line
Spaces collapsed, no effect
Trailing U+00A0 padding
Unpredictable: breaks mid-item, later line truncated with …
What does work: nested wrap rows move to the next line as a block when they don't fit, so a provider can at least keep groups together. But a wide terminal always gets one line.
It also looks like the footer is capped at 3 lines (further content is truncated with …). If that's intentional, it would help to document it in the create-statusline skill.
Activity