[Bug] Numpad Enter Key Produces Invalid Character Input Instead of Sending Message

Status Fixed / completed
Reported on v2.1.2
Maintainer reply ✓ Yes — blois
Activity 4 comments · opened Jan 9, 2026 · closed Jan 15, 2026
💡 Likely answer: A maintainer (blois, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
When hitting enter on my numpad it comes up with a [57414u and does not send the message. Very annoying. Thanks!

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.2
  • Feedback ID: 9b5bce1d-ad98-4077-8afd-6489205f243d

Errors

[]

View original on GitHub ↗

4 Comments

github-actions[bot] · 9 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/17040
  2. https://github.com/anthropics/claude-code/issues/17101
  3. https://github.com/anthropics/claude-code/issues/16843

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

scttbnsn · 9 months ago

Confirming this affects more than just numpad Enter. I'm also seeing issues with the AskUserQuestion "Other" text input - when typing custom text in the free-form input option, it advances/submits after typing just a single character.

Environment:

  • Claude Code: 2.1.x
  • Terminal: Ghostty
  • Platform: macOS (Darwin 25.2.0)

Workaround that fixed both issues:

Add these keybinds to ~/.config/ghostty/config:

keybind = enter=text:\r
keybind = shift+enter=text:\x1b\r
keybind = shift+space=text:\x20
keybind = kp_enter=text:\r

This forces Ghostty to send legacy terminal escape sequences instead of Kitty protocol sequences for these keys. After adding these and restarting Ghostty, both numpad Enter and custom text input work correctly.

blois collaborator · 9 months ago

This should be fixed on the latest version.

github-actions[bot] · 8 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.