[BUG] Pressing Enter to confirm IME (Japanese) conversion unintentionally sends the prompt

Status Fixed / completed
Maintainer reply None cached
Activity 6 comments · opened Sep 29, 2025 · closed Oct 6, 2025

Preflight Checklist

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

What's Wrong?

When typing in Japanese (using an IME) in the VS Code extension's chat input field, pressing the Enter key to confirm a character conversion sends the prompt prematurely. This occurs even when I am in the middle of composing a sentence, making it extremely difficult to type complex questions that require multiple text conversions.

What Should Happen?

The Enter key should not send the prompt when the Input Method Editor (IME) is active for text composition. Its only function should be to confirm the selected characters (e.g., finalizing a Kanji conversion). Sending the prompt should be a distinct action performed only after the user has finished typing.

Error Messages/Logs

No specific error messages or logs are generated. This is a UI behavioral issue.

Steps to Reproduce

  1. Open the Claude Code extension on Mac and show the chat panel in VS Code.
  2. Focus on the chat input field.
  3. Switch the PC's input method to Japanese (turn on IME).
  4. Type a Japanese phrase that requires conversion, for example, "kakuchoukinou".
  5. As the IME suggests conversion candidates (e.g., 「拡張機能」), press the Enter key to confirm the selection.
  6. The prompt is immediately sent with only the confirmed text ("拡張機能"), even though the intention was to continue typing the rest of the sentence.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.0

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

This issue occurs within the VS Code GUI (the chat input box) and is not dependent on a specific terminal or shell. This issue likely affects users of many languages that rely on an Input Method Editor (IME) where the Enter key is used for text composition, such as Chinese and Korean. This behavior significantly degrades the user experience and usability of the extension for speakers of these languages.

View original on GitHub ↗

6 Comments

github-actions[bot] · 11 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/7612
  2. https://github.com/anthropics/claude-code/issues/2054

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

nerikosans · 11 months ago

Hi, thank you for opening this issue.
Let me just elaborate on the problem a little bit for clarity:

The Japanese input process involves two distinct steps: composition and conversion.

  • Composition: The user types phonetic characters (Hiragana) using standard letter keys (a-z).
  • Conversion: The user presses the spacebar to view Kanji candidates and then presses the Enter key (here is the problem) to confirm a selection. This action finalizes the characters in the input field but is not intended to submit the form.

After the full text is composed, the user presses the Enter key a second time to submit the form.

Therefore, listening for all Enter key presses to trigger a submission will create confusing and unintended behavior for Japanese users. 😭

FYI: https://dninomiya.github.io/form-guide/stop-enter-submit

Current behavior

!Image

Expected behavior

!Image

cotton123236 · 11 months ago

Same issue in Traditional Chinese!
Please fix this problem ASAP 😭😭

NozNozNozNoz · 11 months ago

Just checked in version 2.0.5 and it's working perfectly now. Thanks a ton for the super quick turnaround on this !!! I will close this issue in 3 days if there are no further related problems.

NozNozNozNoz · 10 months ago

Confirmed that this is resolved in the VS Code extension version 2.0.5. Closing now.

github-actions[bot] · 10 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.