codex - 💡(How to fix) Fix Feature request: colored TUI status line style [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20012Fetched 2026-04-29 06:23:45
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×4unlabeled ×2commented ×1

Code Example

[tui]
status_line = [
  "project-name",
  "current-dir",
  "git-branch",
  "model-with-reasoning",
  "five-hour-limit",
  "weekly-limit",
  "context-remaining",
  "used-tokens",
]
status_line_style = "colored"
RAW_BUFFERClick to expand / collapse

Feature request

Codex already lets users choose TUI status line fields via tui.status_line, but the rendered line is muted/monochrome. Dense status lines are much easier to scan when fields like model, cwd, git branch, rate limits, and context usage carry semantic color.

Proposed behavior

Add an opt-in style option that preserves the current default:

[tui]
status_line = [
  "project-name",
  "current-dir",
  "git-branch",
  "model-with-reasoning",
  "five-hour-limit",
  "weekly-limit",
  "context-remaining",
  "used-tokens",
]
status_line_style = "colored"

I prepared an upstream-ready branch on my fork:

The branch adds tui.status_line_style = "colored", renders configured status line segments as styled spans using Codex's approved TUI palette, updates the generated config schema/docs, and adds config/render tests.

Validation run on the branch

  • just fmt
  • just write-config-schema
  • just fix -p codex-tui
  • cargo test -p codex-tui
  • cargo test -p codex-core tui_status_line_style_deserializes_from_toml

I tried to open a draft PR from the fork, but GitHub rejected CreatePullRequest for my account/token against openai/codex even though the fork branch is public.

extent analysis

TL;DR

To add colored status line fields, merge the proposed branch wesleysmyth:codex/statusline-colored-style into the main repository.

Guidance

  • Review the proposed branch and its changes to ensure they align with the desired behavior.
  • Verify the added status_line_style option in the tui configuration section works as expected.
  • Test the rendering of status line segments with the new colored style.
  • Check the generated config schema and documentation for accuracy.

Example

No code snippet is provided as the issue already includes a TOML configuration example:

[tui]
status_line = [
  "project-name",
  "current-dir",
  "git-branch",
  "model-with-reasoning",
  "five-hour-limit",
  "weekly-limit",
  "context-remaining",
  "used-tokens",
]
status_line_style = "colored"

Notes

The proposed branch has already been validated with various tests, including cargo test and just fmt.

Recommendation

Apply the workaround by merging the proposed branch, as it provides the desired functionality and has been thoroughly tested.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature request: colored TUI status line style [1 comments, 2 participants]