[CRITICAL] Korean IME: Composing characters display at wrong position (unusable for Korean users)
CRITICAL for Korean Users
This issue makes Claude Code practically Annoying for Korean users.
Every single character typed requires looking away from the cursor position to see what's being typed.
--> What's ridiculous is that they already released 2.0.68, saying they fixed this issue.
It's still not fixed in v2.1.6
Description
When typing Korean using IME, composing characters (incomplete/in-progress characters) display at the wrong position - they appear on the next line at the beginning, instead of at the current cursor position.
Once the character is finalized, it jumps to the correct cursor position.
But during composition, it's misplaced, making typing extremely annoying.
Expected Behavior
Composing characters should display at the cursor position (simple)
Actual Behavior
Composing characters appear far away from the cursor (next line, beginning of line).
Environment
- OS: Windows 11
--> Local ; VS Code, Antigravity integrated-terminal, Windows terminal, pwsh, etc.
--> WSL2 ; VS Code, Antigravity integrated-terminal, zsh, warp, bash, etc.
- Claude Code Cli : Local installation
- IME: Windows Korean IME
Reproduction
- Launch Claude Code
- Type Korean characters
- Observe composing characters appear at wrong position
Reproduction rate: Always 100% (every single Korean character)
Impact
- Usability: CRITICAL
- Affected users: All Korean language users
- Workaround: just ignore the screen and type, remembering it in my head.
- Makes the product essentially very very annoying for Korean input
Additional Info
- VS Code's Terminal handles Korean IME correctly (shows composing chars at cursor)
- Windows Terminal handles Korean IME correctly (shows composing chars at cursor)
- WSL: ZSH terminal handles Korean IME correctly (shows composing chars at cursor)
- Issue only occurs in Claude Code
- English input works normally
** Should be a simple fix: display composing characters at cursor position.
This issue has 11 comments on GitHub. Read the full discussion on GitHub ↗