[Bug] Hangul backspace leaves blank cells and cursor mismatch in Codex CLI (Rocky9 + MobaXterm)

Resolved 💬 3 comments Opened Oct 7, 2025 by rtl-ai Closed Oct 8, 2025

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

v0.45.0

Which model were you using?

gpt-5-codex (high)

What platform is your computer?

Linux 5.14.0-503.31.1.el9_5.x86_64 x86_64 x86_64

What steps can reproduce the bug?

Start codex in an SSH session from MobaXterm to a Rocky Linux 9 host.

Type: 문자열 테스트 입니다. 이제 글자를 지우겠습니다.

Press Backspace a few times.

Observe the editing area.

What is the expected behavior?

Each Backspace removes one whole Hangul syllable. Cursor and delete position match. No leftover blanks.

!Image

What do you see instead?

Blank cells remain in the edited line. The visual cursor position diverges from the actual delete position while backspacing.

!Image

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#4870
#3260

Powered by Codex Action

rtl-ai · 10 months ago

Not a duplicate.

My case: Linux (Rocky Linux 9) over SSH via MobaXterm, TERM=xterm, ko_KR.UTF-8. Backspace in Codex CLI leaves blank cells and cursor mismatch. Plain shell behaves correctly.
#4870: Windows IME preedit rendering blanks/disappears. Different OS and code path; not about backspace redraw.
#3260: Japanese IME composition drops digits. Different input path and symptom.

Artifacts attached: Animation4/5.gif,
Codex CLI: 0.45.0.
Marking as related, not duplicate.

dylan-hurd-oai contributor · 10 months ago

(Note: this comment was generated by Codex.)

Thanks for the detailed report! This appears related to #4870, which tracks Korean IME/rendering issues in the CLI. To keep the investigation centralized, we’ll track it in #4870. If you think this is an incorrect diagnosis or your case is distinct, please reply here and we’ll separate it out.