Windows Terminal Input And Render Bug
Resolved 💬 5 comments Opened Oct 15, 2025 by ptlzc Closed Jan 10, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.46.0
Which model were you using?
_No response_
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
When I paste multi-line text into the Codex terminal on Windows Terminal, the first newline is interpreted as a submit action instead of inserting a line break. As a result, only the first line is sent and the rest is not entered as intended.
When using a Chinese IME, after committing a character, pressing Space causes the previously entered character to render as a blank (disappear visually) in the input field. This looks like a preview/rendering glitch.
<img width="2153" height="385" alt="Image" src="https://github.com/user-attachments/assets/f166b628-c251-4c0f-96d3-ad7a97fdc161" />
What is the expected behavior?
copy multiple text line then paste to codex terminal
What do you see instead?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Hey, the Chinese IME problem will be fixed by #4921. I haven't checked the other issue yet.
@joshka-oai
Still bug on v0.47.0
win11
bug in cmd and PowerShell
Git Bash is good for input, but has a bug when deleting[it can only delete the current line]
Git Bash doesn't give any character in the terminal until the word is complete.
Maybe bug cause like this, it's like pre-render, but not necessary for Chinese ime
<img width="586" height="516" alt="Image" src="https://github.com/user-attachments/assets/79e80936-659d-41c5-b0c8-708fe288b0f4" />
Sometimes, like this, in CMD when you click space, it will make the last character disappear half.
<img width="537" height="111" alt="Image" src="https://github.com/user-attachments/assets/c5b4e5bd-9c49-4373-bc57-4c67e6596970" />
The fix is applied to our main branch and will be in the next release (0.48)
Closing old issue.