Codex use UTF-8 BOM by default and change Chinese to unreadable nonsenese
Resolved 💬 3 comments Opened Mar 27, 2026 by UIZorrot Closed Jul 2, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
latest
What subscription do you have?
plus
What platform is your computer?
windows, wsl
What issue are you seeing?
just let codex or gpt know, please use UTF-8 with no BOM by default.
What steps can reproduce the bug?
let codex do some chinese work and you will see. May other utf-8 language have this issue.
What is the expected behavior?
just let codex or gpt know, please use UTF-8 with no BOM by default. And when using command like get-content, should use utf-8 for non-english language.
Additional information
<img width="726" height="1020" alt="Image" src="https://github.com/user-attachments/assets/966e701a-2444-4b4b-bc75-50ce23660b58" />
like this
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I prepared a fix for this on my fork, but this repository is currently configured to block PRs from non-collaborators
Branch:
https://github.com/mbetrifork/codex-fixes/tree/issue-15967
Commit:
a8eaccf8e Fix #15967: default PowerShell commands to UTF-8
Summary:
Get-Content/UTF-8-no-BOM read path that can garble Chinese and other non-ASCII text on Windows PowerShellI can make a patch file if that's the only way to contribute the fix.
bad that utf-8 md files is mojibaked EVERY time in codex Powershell calls. Fix wanted