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
Color diff in Warp terminal is unreadable in the new version (Windows) #12904
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
Reacted by Ignat Remizov, Alex Kryvdyk, dewspbru, lusipad and Steve Mostovoy
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. :(
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?)
Reacted by Ignat Remizov, dewspbru, Steve Mostovoy, Ali Uyar and zhutao100
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.
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.
I tried the suggested workaround of forcing 256-color terminfo, and also tested what happens when I remove truecolor signaling.
Case A (baseline, less “toxic” background)
Start Codex normally in WezTerm / PowerShell 5.1. In my case the environment contained:
TERM=xterm-256 (when set for the session)
COLORTERM=truecolor
In this mode the diff background blocks were still present, but the green/red looked noticeably darker and more readable (see Screenshot A).
Case B (forced “no truecolor”, background becomes more “toxic”)
I restarted Codex with TERM=xterm-256 and explicitly removed COLORTERM before launching Codex. Then I ran a minimal probe via Codex harness to capture the effective environment seen by both cmd.exe and PowerShell (absolute path).
In this mode the same TUI diff background rendering became much more “toxic” (pure bright green / bright red fills), making diffs harder to read (see Screenshot B).
Conclusion / Why this matters
TERM=xterm-256 is successfully propagated into the Codex Windows harness (cmd.exe) and into PowerShell when invoked by absolute path.
Removing COLORTERM=truecolor changes Codex’s background coloring behavior, but does not fix the underlying issue. It actually makes backgrounds more aggressive in my setup.
This suggests the problem is in Codex TUI’s diff background color selection / theming (and how it chooses between truecolor vs 256-color paths), not in the terminal theme itself.
(Attached: Screenshot A = less toxic, Screenshot B = more toxic.)
Thanks to @tagor-sian for the guidance. The root cause of this UI glitch is that the application lacks proper "color fallback" adaptation. Here is the technical breakdown:
The Technical Reality: Truecolor vs. ANSI 16
Truecolor (24-bit): Supports 16 million colors, allowing for the subtle, soft "dark red/green" backgrounds intended by the developers.
ANSI 16-color: A legacy standard with a very limited palette of high-saturation, high-brightness colors (the "flashbang" colors we are seeing).
The Developer's Blind Spot
The Codex developers likely work on modern terminals (macOS or optimized Linux environments) where Truecolor is the default. The "soft dark highlights" they chose look great in those environments, so the code was pushed as-is.
The Windows/Environment Issue
On many Windows systems (or environments where COLORTERM isn't explicitly set), the underlying UI library assumes the terminal is legacy and doesn't support Truecolor. To be "safe," it automatically downgrades the colors.
The Disaster (Forced Mapping)
Since the library is forced to use the 16-color palette, it performs a crude "forced mapping." It maps the developer's sophisticated, soft shades to the nearest available basic colors—which happen to be the eye-searing, neon-bright "Red" and "Green."
Temporary Workaround for Users
If you are using PowerShell, you can manually force Truecolor support by running the following command before launching Codex:
$env:COLORTERM="truecolor"
This should restore the intended soft color scheme. Hopefully, the developers can implement a fix to handle this fallback more gracefully!
Thanks to @tagor-sian for the guidance. The root cause of this UI glitch is that the application lacks proper "color fallback" adaptation. Here is the technical breakdown:
The Technical Reality: Truecolor vs. ANSI 16
Truecolor (24-bit): Supports 16 million colors, allowing for the subtle, soft "dark red/green" backgrounds intended by the developers.
ANSI 16-color: A legacy standard with a very limited palette of high-saturation, high-brightness colors (the "flashbang" colors we are seeing).
The Developer's Blind Spot
The Codex developers likely work on modern terminals (macOS or optimized Linux environments) where Truecolor is the default. The "soft dark highlights" they chose look great in those environments, so the code was pushed as-is.
The Windows/Environment Issue
On many Windows systems (or environments where COLORTERM isn't explicitly set), the underlying UI library assumes the terminal is legacy and doesn't support Truecolor. To be "safe," it automatically downgrades the colors.
The Disaster (Forced Mapping)
Since the library is forced to use the 16-color palette, it performs a crude "forced mapping." It maps the developer's sophisticated, soft shades to the nearest available basic colors—which happen to be the eye-searing, neon-bright "Red" and "Green."
Temporary Workaround for Users
If you are using PowerShell, you can manually force Truecolor support by running the following command before launching Codex:
$env:COLORTERM="truecolor"
This should restore the intended soft color scheme. Hopefully, the developers can implement a fix to handle this fallback more gracefully!
I found this.https://github.com/aofp/yume
Helps a little so you can read the diff without suffering from the stupid background until an update is released.
Activity
github-actions commentedon Feb 26, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
ansitheme is rendered as explicit RGB colors instead of terminal ANSI palette indices #12890Powered by Codex Action
Felix3322 commentedon Feb 26, 2026
try /theme
tomasmarekk commentedon Feb 26, 2026
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 commentedon Feb 26, 2026
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 commentedon Feb 26, 2026
My eyes are begging for mercy.
tummetott commentedon Feb 26, 2026
#12912
ignatremizov commentedon Feb 26, 2026
#12749 (comment)
tagorr commentedon Feb 26, 2026
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 commentedon Feb 26, 2026
For those of you using Windows Terminal can you try running
set TERM=xterm-256first and then running codex and report if it improves? Should look more like what you see in the WezTerm example above.tagorr commentedon Feb 26, 2026
Environment
What I tested
I tried the suggested workaround of forcing 256-color terminfo, and also tested what happens when I remove truecolor signaling.
Case A (baseline, less “toxic” background)
Start Codex normally in WezTerm / PowerShell 5.1. In my case the environment contained:
TERM=xterm-256(when set for the session)COLORTERM=truecolorIn this mode the diff background blocks were still present, but the green/red looked noticeably darker and more readable (see Screenshot A).
Case B (forced “no truecolor”, background becomes more “toxic”)
I restarted Codex with
TERM=xterm-256and explicitly removedCOLORTERMbefore launching Codex. Then I ran a minimal probe via Codex harness to capture the effective environment seen by bothcmd.exeand PowerShell (absolute path).Probe output (raw):
In this mode the same TUI diff background rendering became much more “toxic” (pure bright green / bright red fills), making diffs harder to read (see Screenshot B).
Conclusion / Why this matters
TERM=xterm-256is successfully propagated into the Codex Windows harness (cmd.exe) and into PowerShell when invoked by absolute path.COLORTERM=truecolorchanges Codex’s background coloring behavior, but does not fix the underlying issue. It actually makes backgrounds more aggressive in my setup.(Attached: Screenshot A = less toxic, Screenshot B = more toxic.)
1 remaining item
acgxv commentedon Feb 27, 2026
Dup of #12749
ignatremizov commentedon Feb 27, 2026
As mentioned in #12749, I implemented a fix in ignatremizov#1 but cannot open a PR here
HCID274 commentedon Feb 27, 2026
Thanks to @tagor-sian for the guidance. The root cause of this UI glitch is that the application lacks proper "color fallback" adaptation. Here is the technical breakdown:
The Technical Reality: Truecolor vs. ANSI 16
The Developer's Blind Spot
The Codex developers likely work on modern terminals (macOS or optimized Linux environments) where Truecolor is the default. The "soft dark highlights" they chose look great in those environments, so the code was pushed as-is.
The Windows/Environment Issue
On many Windows systems (or environments where
COLORTERMisn't explicitly set), the underlying UI library assumes the terminal is legacy and doesn't support Truecolor. To be "safe," it automatically downgrades the colors.The Disaster (Forced Mapping)
Since the library is forced to use the 16-color palette, it performs a crude "forced mapping." It maps the developer's sophisticated, soft shades to the nearest available basic colors—which happen to be the eye-searing, neon-bright "Red" and "Green."
Temporary Workaround for Users
If you are using PowerShell, you can manually force Truecolor support by running the following command before launching Codex:
This should restore the intended soft color scheme. Hopefully, the developers can implement a fix to handle this fallback more gracefully!
Felix3322 commentedon Feb 27, 2026
this works
immapolar commentedon Feb 27, 2026
I found this. https://github.com/aofp/yume
Helps a little so you can read the diff without suffering from the stupid background until an update is released.
fix(tui): promote windows terminal diff ansi16 to truecolor (openai#1…
[pull] main from openai:main (#16)
[pull] main from openai:main (#16) (#17)
fix(tui): promote windows terminal diff ansi16 to truecolor (#13016)
fix(tui): promote windows terminal diff ansi16 to truecolor (openai#1…
fix(tui): promote windows terminal diff ansi16 to truecolor (#13016)