Regression: Codex CLI 0.133.0 hides/flickers text in Windows Terminal; 0.130.0 works

Resolved 💬 5 comments Opened May 25, 2026 by ace1573 Closed May 27, 2026

What version of Codex CLI is running?

Broken: codex-cli 0.133.0

Works after rollback: codex-cli 0.130.0

Platform

  • OS: Microsoft Windows NT 10.0.19045.0
  • Shell: PowerShell 7.6.2
  • Terminal: Windows Terminal
  • Code page: 65001 / UTF-8

What issue are you seeing?

After upgrading Codex CLI to 0.133.0, text rendering in the TUI becomes unstable on Windows Terminal.

Symptoms:

  • While typing Chinese text with IME, previously typed text can become visually hidden.
  • During dynamic status rendering, text flickers or partially disappears.
  • During startup, the Booting MCP status line can render incorrectly. For example, only CP remains visible from Booting MCP.
  • The input still appears to work logically, but the terminal display is corrupted until another repaint happens.

Rolling back to codex-cli 0.130.0 fixes the issue on the same machine, same terminal, same shell, and same project.

Steps to reproduce

  1. Install Codex CLI 0.133.0.
  2. Run codex in Windows Terminal / PowerShell.
  3. Type Chinese text using Microsoft Pinyin IME.
  4. Observe previous characters hiding/flickering.
  5. Restart Codex and observe startup/status text such as Booting MCP sometimes partially disappearing.
  6. Roll back to 0.130.0:

``powershell
npm i -g @openai/codex@0.130.0
``

  1. Run Codex again and observe that the rendering problem is gone.

Expected behavior

Text should remain visible and stable while typing, refreshing status lines, and booting MCP.

Actual behavior

Text is partially hidden or flickers in Codex CLI 0.133.0. The same environment works correctly after downgrading to 0.130.0.

Additional context

This appears related to previous Windows TUI / IME rendering issues, but this report identifies a newer regression range:

  • Works: 0.130.0
  • Broken: 0.133.0

Possibly related:

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗