Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C063 Supported 2026-11-08

GitHub issue #45163 in openai/codex, opened 2026-09-13 by lightninglu10, records a report that in codex-cli 0.154.0 on macOS, Darwin 25.6.0, arm64, after the terminal changes between light and dark appearance while Codex is already running, the composer and previously rendered user-message blocks retain their old background colors, that the terminal default foreground updates, producing nearly white text on a pale background, so long-lived sessions become unreadable after an automatic macOS appearance change, that refocusing and redrawing do not refresh the cached palette, and that restarting refreshes the startup colors but the next appearance change can break the session again.

Verbatim Excerpts from Cited Records
“After the terminal changes between light and dark appearance while Codex is already running, the composer and previously rendered user-message blocks retain their old background colors.”
— lightninglu10 · openai/codex (issue 45163 opening body, What issue are you seeing? section) · 2026-09-13T04:23:36Z ·GitHub Issue ↗
“The terminal's default foreground updates, producing nearly white text on a pale background (or the inverse mismatch). Long-lived sessions become unreadable after an automatic macOS appearance change.”
— lightninglu10 · openai/codex (issue 45163 opening body, What issue are you seeing? section) · 2026-09-13T04:23:36Z ·GitHub Issue ↗
“Refocusing and redrawing do not refresh the cached palette. Restarting/resuming refreshes the startup colors, but the next appearance change can break the session again.”
— lightninglu10 · openai/codex (issue 45163 opening body, What issue are you seeing? section) · 2026-09-13T04:23:36Z ·GitHub Issue ↗
“This follows up my earlier report **#37298**, which described a failed refresh permanently poisoning the color cache in 0.146.0. The current implementation has a different failure mode: focus-driven refresh has been removed entirely, so no transient failure is required.”
— lightninglu10 · openai/codex (issue 45163 opening body, What issue are you seeing? section) · 2026-09-13T04:23:36Z ·GitHub Issue ↗
Counter-record: Issue remains open with 26 comments as of 2026-11-07; the API returned all 26. No maintainer response appears in the surveyed thread. Reporters reproduced it from 2026-09-15 to 2026-11-07 across codex-cli versions up to 0.167.0 (source check) and terminals including WezTerm, tmux, and WebSSH; #45291 was closed as a duplicate of this issue. Community members linked untested fork patches for crossterm DECSET 2031 support; no maintainer fix or closure decision appears in the surveyed thread. The most recent comment (2026-11-07, cliqsales) reports the same unreadable-composer pattern on 0.160.1 in tmux without isolating the trigger. The claim documents only the original report, not a verified current state. Falsification probe: If issue 45163 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests