Chinese text rendering corruption in Linux CLI terminal session
Open 💬 4 comments Opened Apr 5, 2026 by Kirito-Elucidator
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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:
- It seems to affect Chinese text primarily.
- It usually appears after a relatively long conversation/session.
- When the cursor moves over the garbled area, that area may redraw and recover.
- In the same terminal session,
exit+codex resumedoes not fix it. - 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?
- Start Codex CLI in Linux under VS Code integrated terminal.
- Use Chinese text in prompts/responses.
- Keep chatting for a longer session.
- Observe that parts of Chinese text may render as garbled/corrupted.
- Try
exitthencodex resumein the same terminal session -> issue persists. - 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" />
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
If you're able to repro, please use
/feedbackto upload the session details and post the thread ID here. This will allow us to determine whether this is model behavior or a TUI bug.Thanks a lot for the quick response and clarification!
Sorry, I completely forgot about the
/feedbackfeature 🙈 I’ll use it next time. Really appreciate your help!Hi again! I managed to reproduce the bug today.
As requested, I've used the
/feedbackcommand to upload the session details. Here is the thread ID:019da0df-9569-77a0-9126-dbd560f96685