[BUG] When pressing the numpad Enter key in Claude Code, it inserts the literal text [57414u instead of submitting input. The regular Enter key works correctly.
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?
Environment:
- OS: macOS (Darwin 24.6.0)
- Claude Code version: 2.1.3
- Keyboard: Wooting Two HE AVR
Expected behavior:
Numpad Enter should behave identically to the main keyboard Enter key (and did before)
Actual behavior:
Numpad Enter inserts the literal characters [57414u into the input field.
Technical details:
The sequence [57414u is a CSI u-sequence from the kitty keyboard protocol (enhanced keyboard mode). This suggests Claude Code is enabling the enhanced keyboard protocol via escape sequences but not properly decoding the responses.
Specifically:
- Claude Code appears to send ESC [ > 1 u to enable CSI u mode
- When numpad Enter is pressed, the terminal sends ESC [ 57414 u
- Claude Code isn't parsing this sequence and instead displays it literally
Workaround:
Use the regular Enter key instead of numpad Enter.
Note:
This works correctly in iTerm2, suggesting it's specific to Claude Code's terminal input handling.
What Should Happen?
I hit the number pad return and it acts like the same function as the enter key.
Error Messages/Logs
It doesn't count as a retun when selecting an option, or inputs "[57414u" as text on hitting the key
Steps to Reproduce
Hit the return key on a a mac on wooting two he keyboard
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.3
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗