Chinese text rendering corruption in Linux CLI terminal session

Open 💬 4 comments Opened Apr 5, 2026 by Kirito-Elucidator

What version of Codex CLI is running?

0.118.0

What subscription do you have?

Business

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Linux 5.15.0-139-generic x86_64 x86_64

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

VSCode

What issue are you seeing?

Chinese text in Codex CLI sometimes renders as garbled/corrupted-looking characters.

Key behavior:

  1. It seems to affect Chinese text primarily.
  2. It usually appears after a relatively long conversation/session.
  3. When the cursor moves over the garbled area, that area may redraw and recover.
  4. In the same terminal session, exit + codex resume does not fix it.
  5. If I open a brand-new terminal tab/window in VS Code and run codex resume, rendering becomes normal immediately.

This suggests a terminal-session-local rendering/state issue in TUI (redraw/state corruption), not actual conversation content corruption.

What steps can reproduce the bug?

  1. Start Codex CLI in Linux under VS Code integrated terminal.
  2. Use Chinese text in prompts/responses.
  3. Keep chatting for a longer session.
  4. Observe that parts of Chinese text may render as garbled/corrupted.
  5. Try exit then codex resume in the same terminal session -> issue persists.
  6. Open a new terminal tab/window and run codex resume -> display returns to normal.

What is the expected behavior?

Chinese text should render correctly and consistently, and exit/resume in the same terminal should not keep corrupted rendering state.

Additional information

  • Cursor movement over corrupted text can trigger local recovery.
  • A new terminal session fixes it immediately.
  • The original terminal session keeps the bad rendering state.
  • Screenshot attached below.

<img width="1259" height="140" alt="Image" src="https://github.com/user-attachments/assets/c28481a2-c5ed-4ab8-959d-e4c63593b4be" />

View original on GitHub ↗

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