IME Enter key bypasses keybindings in Confirmation UI (Plan comments, AskUserQuestion)
Resolved 💬 3 comments Opened Mar 20, 2026 by kkido88 Closed Mar 20, 2026
Description
The fix for IME Enter key handling (PR #8480) resolved the issue in the main chat input, but the same problem persists in Confirmation-context UI dialogs in the desktop app.
Affected Areas
- Plan mode comment input — the text field shown via "Tell Claude what to do instead" (代わりにClaudeに何をすべきか指示する)
- AskUserQuestion "Other" text input — when typing a custom response to agent questions
Steps to Reproduce
- Use Japanese IME (or other CJK IME) on macOS
- Enter plan mode and get a plan proposal
- Select "Tell Claude what to do instead" to type feedback
- Type Japanese text and press Enter to confirm IME conversion
- Actual: The Enter key is captured as submission (
confirm:yes), sending the incomplete/unintended message - Expected: Enter only confirms IME composition; a separate key (e.g., Cmd+Enter) submits
Same behavior occurs in the AskUserQuestion "Other" text input.
Workaround Attempted
Setting "enter": null in the Confirmation context via ~/.claude/keybindings.json has no effect, suggesting the Enter handler in these dialogs bypasses the keybinding system:
{
"bindings": [
{
"context": "Confirmation",
"bindings": {
"enter": null,
"meta+enter": "confirm:yes"
}
}
]
}
Environment
- Claude Code v2.1.76 (Desktop App, macOS)
- macOS Japanese IME
Context
- Related: #8405 (locked), PR #8480 (fix for chat input)
- The main chat input (
Chatcontext) works correctly after the fix — this issue is isolated toConfirmation-context dialogs - Many Japanese users have reported the general IME Enter issue on X/Twitter, but those reports are primarily about chat input / VS Code extension, which are now fixed
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗