Claude Code Korean Text Issues — How It Differs From Codex and How to Fix It
Claude Code has its own Korean encoding quirks, but they’re fundamentally different from Codex. Here’s what breaks, why, and how to fix it.
Claude Code Has Korean Text Issues Too
If you've dealt with Codex's Korean encoding problems, you might assume Claude Code is fine since it runs locally. Not quite.
Claude Code does have Korean text issues — but the root causes are completely different from Codex.
Codex vs Claude Code — Why Korean Breaks Differently
The architectural difference changes everything about how Korean text is handled.
| Aspect | Codex | Claude Code |
|---|---|---|
| Execution | Cloud sandbox (container) | Local terminal (your machine) |
| Locale | Forced C.UTF-8 / en_US.UTF-8 | Inherits system locale |
| Main cause | Sandbox locale mismatch | Rust byte-boundary splitting bug |
| EUC-KR files | Assumes UTF-8, corrupts CP949 | Local tools handle it fine |
| Fix responsibility | User must pre-convert files | Anthropic-side patches |
Codex's environment is fundamentally hostile to Korean text. Claude Code runs on your machine, so locale issues don't apply — but it has a separate streaming bug that corrupts Korean characters.
What Actually Breaks in Claude Code
Rust Byte-Boundary Splitting (U+FFFD Replacement)
Claude Code is built in Rust. Korean characters take 3 bytes in UTF-8. When streamed JSON chunks split at byte boundaries, multibyte characters get cut in half, producing U+FFFD (�) replacement characters.
A major fix was shipped in April 2026, but intermittent recurrences have been reported.
macOS Korean Folder Name Normalization
macOS uses NFD (decomposed) Unicode for its filesystem. A folder named "한글" gets stored in NFD form, which can mismatch against Claude Code's internal NFC (composed) path matching logic.
Windows Korean Username Paths
If your Windows username contains Korean characters (e.g., C:\Users\김철수\), Claude Code can crash when processing the path.
Glob Pattern Matching Failure With CJK
Claude Code's file search (Glob tool) fails to correctly match wildcard patterns containing Korean or CJK characters.
Fixes You Can Apply Right Now
Verify Terminal UTF-8
Claude Code inherits your system locale. Make sure your terminal is set to UTF-8.
[code lang="bash"]
macOS / Linux
echo $LANG
Should show ko_KR.UTF-8 or en_US.UTF-8
If not set
export LANG=en_US.UTF-8 export LC_ALL=en_US.UTF-8 [/code]
Avoid Korean Folder Names (macOS)
If your project directory contains Korean characters, rename it to ASCII. This sidesteps the NFD/NFC normalization mismatch entirely.
Windows Korean Username Workaround
Create a separate English-named user account, or override the USERPROFILE environment variable to point to an ASCII path.
Keep Claude Code Updated
The U+FFFD streaming fix landed in April 2026. Always run the latest version.
[code lang="bash"]
Check version
claude --version
Update if installed via npm
npm update -g @anthropic-ai/claude-code [/code]
What Codex Users Should Know When Switching
If you've been fighting Codex's Korean encoding, here's what changes with Claude Code.
- Legacy EUC-KR/CP949 files: Codex forced UTF-8 reads, corrupting everything. Claude Code uses your local filesystem, so tools like
iconvwork normally - Korean variable names and comments: Codex's sandbox locale made these unreliable. Claude Code runs locally, so they work as expected
- File I/O: Codex sandboxed all file operations with limited encoding control. Claude Code reads and writes through your system's native filesystem
The one new issue is intermittent U+FFFD corruption in streamed output — a Claude Code–specific bug that Codex didn't have.
Known GitHub Issues (May 2026)
These are the active Korean/CJK issues in the Claude Code repository as of May 2026.
| Issue | Description | Status |
|---|---|---|
| #55949 | Korean values dropped from OTEL telemetry | Open |
| #55588 | Glob tool fails on Korean wildcard patterns | Open |
| #55508 | Korean broken in pptx/docx preview (macOS) | Open |
| #55388 | Conversation search can't find CJK strings | Open |
Most are still open, but Anthropic has been actively shipping fixes.
The Bottom Line
Claude Code's Korean issues are fundamentally different from Codex. Codex broke Korean at the environment level — forced locale, sandboxed file I/O, no escape hatch. Claude Code runs locally, so most things just work. The remaining issues are Rust streaming bugs, macOS path normalization, and Windows path handling. Apply the fixes above, keep your installation updated, and you'll avoid most problems.