claude-code - 💡(How to fix) Fix [BUG] Vietnamese character input issues in Interactive Mode (IME Handling) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45093Fetched 2026-04-09 08:13:27
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

I am experiencing issues when typing Vietnamese characters while in the Claude CLI's interactive mode on Windows (PowerShell/Windows Terminal).

What Should Happen?

The CLI should properly handle IME composition events or provide a way to bypass raw key interception for non-Latin character inputs. Many Node-based CLIs solve this by using libraries that better support Windows' native input handling.

Error Messages/Logs

Steps to Reproduce

While Vietnamese input works perfectly fine in the standard PowerShell prompt, once I enter the interactive session by running claude, the input becomes buggy. Specifically:

  • Characters are dropped or deleted while typing (likely due to how the CLI handles Backspace/Input events from IMEs like Unikey or EVKey).
  • Diacritics (tone marks) cause the cursor to jump or the entire word to disappear.
  • This is a common issue in Node.js CLI tools that intercept raw keypresses without proper IME support.
  • Steps to Reproduce:
    • Open PowerShell or Windows Terminal on Windows.
    • Ensure a Vietnamese IME (like Unikey or EVKey) is active using Telex or VNI input methods.
    • Run claude to enter interactive mode. Try to type a Vietnamese word with marks, e.g., "tiếng Việt". Observe that characters are mangled or deleted as you type. Environment: OS: Windows 10/11 Terminal: PowerShell / Windows Terminal Claude CLI Version: [Điền phiên bản của bạn vào đây, ví dụ: 0.1.x] IME used: Unikey / EVKey (Vietnamese Telex)

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Claude Opus 4.6

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="452" height="79" alt="Image" src="https://github.com/user-attachments/assets/ef8f78fa-c7aa-49e8-96a5-a4aea1c80ef7" />

extent analysis

TL;DR

The issue can likely be mitigated by using a library that better supports Windows' native input handling for non-Latin character inputs in the Claude CLI.

Guidance

  • Investigate using a library like readline or tty with proper IME support to handle input events in the Claude CLI.
  • Consider bypassing raw key interception for non-Latin character inputs to prevent character mangling or deletion.
  • Look into existing Node-based CLIs that handle IME composition events correctly for inspiration or potential solutions.
  • Verify that the issue persists across different Vietnamese IMEs (like Unikey or EVKey) and input methods (Telex or VNI) to ensure the solution works broadly.

Example

No specific code example can be provided without more context on the Claude CLI's implementation, but exploring libraries that handle IME events and input handling in Node.js could offer a starting point.

Notes

The solution may depend on the specific implementation details of the Claude CLI and how it handles input events, which are not provided in the issue. Additionally, testing across various Windows versions, terminals, and IMEs will be crucial to ensure the fix is robust.

Recommendation

Apply a workaround by integrating a library that supports Windows' native input handling for non-Latin characters, as upgrading to a fixed version is not mentioned as an option in the provided context. This approach is recommended because it directly addresses the issue of improper input handling in the Claude CLI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING