## Description Since upgrading to Claude Code 2.1.1, the numpad Enter key no longer submits input. Instead, it outputs the raw escape sequence `[57414u`. The regular Enter key works correctly. ## Environment - **Claude Code version:** 2.1.1 - **Terminal:** iTerm2 - **OS:** macOS ## Steps to Reproduce 1. Open Claude Code in iTerm2 2. Type any input 3. Press the numpad Enter key to submit ## Expected Behavior Numpad Enter should submit input, identical to the regular Enter key. ## Actual

[BUG] Numpad Enter outputs raw escape sequence [57414u in iTerm2 (v2.1.0)

Status Fixed / completed

Reported on v2.1.1

Maintainer reply None cached

Activity 3 comments · opened Jan 8, 2026 · closed Jan 8, 2026

Description

Since upgrading to Claude Code 2.1.1, the numpad Enter key no longer submits input. Instead, it outputs the raw escape sequence [57414u.

The regular Enter key works correctly.

Environment

Claude Code version: 2.1.1
Terminal: iTerm2
OS: macOS

Steps to Reproduce

Open Claude Code in iTerm2
Type any input
Press the numpad Enter key to submit

Expected Behavior

Numpad Enter should submit input, identical to the regular Enter key.

Actual Behavior

The raw escape sequence [57414u is printed to the input field instead of submitting.

Analysis

The 57414u sequence is the keycode for numpad Enter in the kitty keyboard protocol. This suggests Claude Code 2.1.0 may have enabled kitty protocol support but isn't properly handling the numpad Enter keycode.

Related Issues

#614 - iTerm2 keybinding breaks kitty keyboard protocol in other programs
#9549 - Alt-Enter broken in Ghostty, showing raw escape sequences (similar symptom)
#436 - Enter key non-functional in certain conditions

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗