Color diff in Warp terminal is unreadable in the new version (Windows)

[tomasmarekk]

What version of Codex CLI is running?

codex-cli 0.105.0

What subscription do you have?

PRO

Which model were you using?

gpt-5.3-codex-xhigh

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

Warp

What issue are you seeing?

After installing the new version of Codex CLI, the color diff in Warp has become unreadable. This is not a Warp theme issue, I tried all themes that are natively available in Warp terminal.

The colors for bash commands look fine, but the diff itself is unreadable. I’m probably not able to provide more information than this.

What steps can reproduce the bug?

What is the expected behavior?

No response

Additional information

No response

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #Option to disable diff background highlight #12749
• #ansi theme is rendered as explicit RGB colors instead of terminal ANSI palette indices #12890
• #CLI Reinstate v0.98 single reply colorized diff view and permission request #11972

Powered by Codex Action

[Felix3322]

try /theme

[tomasmarekk]

just tried all the themes that are built into Codex CLI. Some of them improve it a bit, but none are perfect, in the sense that they’re all still relatively hard to read. So the issue must be somewhere else. :(

[wronex]

Can confirm theme changes have no effect on background color. They change foreground color, but background stays pure green or screaming red. This was not a problem in the previous version (104?)

[immapolar]

My eyes are begging for mercy.

[tummetott]

#12912

[ignatremizov]

#12749 (comment)

[tagorr]

This is what it looks like in the WezTerm terminal on Windows. Overall, it's not bad, but I would like the ability to customize the theme in detail, as I need and not just choosing from presets.

[fcoury]

For those of you using Windows Terminal can you try running set TERM=xterm-256 first and then running codex and report if it improves? Should look more like what you see in the WezTerm example above.