Feature request: better color-based emphasis in Codex CLI TUI
Resolved 💬 5 comments Opened Nov 12, 2025 by BankBro Closed Dec 7, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
Summary
In the Codex CLI interactive TUI, it is hard to visually distinguish important information from normal text.
Even when the model uses Markdown (headings, bold, lists), most text is rendered with very similar colors/styles, so the output looks almost uniform and flat.
---
Current behavior
- Headings, bold text and normal paragraphs look very similar in color and emphasis.
- It is hard to quickly spot:
- the final conclusion,
- key commands / steps,
- important warnings / notes.
As a result, long answers are visually dense and it’s easy to miss the most important parts.
---
Expected behavior
- Stronger visual emphasis for:
- headings (
#,##,###) - bold text used for conclusions / key phrases
- warnings / important notes
- Or, alternatively:
- a simple way to configure the TUI theme/styles, or
- a built-in “high emphasis / high contrast” preset that makes important content stand out clearly.
---
Additional context
- When comparing Codex CLI TUI with other AI CLIs (e.g. Claude Code CLI) in the same terminal and same color scheme, those tools make important parts (headings, key phrases, warnings) visually stand out much more, while Codex output looks almost uniform.
- Screenshots comparing Codex CLI TUI vs other CLIs in the same terminal:
- codex cli:
<img width="1230" height="906" alt="Image" src="https://github.com/user-attachments/assets/05aedd90-f201-4843-813c-3767ab2913b1" />
- claude code cli:
<img width="1232" height="1356" alt="Image" src="https://github.com/user-attachments/assets/9f45fe6b-2668-47b4-b42b-ed48392a0abe" />
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for the feature request.
It sounds like part of what you want is syntax highlighting for code. That feature is being tracked in #2912.
This feature is really important. We currently have no way to properly read the responses that the large language model gives us.
And right now the community doesn't accept PRs from us, so how can we contribute to make it go live faster?
@Wan9xy, we generally prioritize features based on feedback from the community. If you'd like to see a feature prioritized, please upvote it (add a thumbs-up reaction). This feature has received two upvotes so far. The linked feature has received nearly more than a dozen.
Closing in favor of #2711, which has received more upvotes.