Expected: digits 1 2 3 and a normal Enter/submit
Actual: inserts PUA characters:
• numpad 1/2/3 → (U+E038, U+E039, U+E03A)
• numpad Enter → (U+E046)
Notes:
• Top number row works fine
• Same keyboard works correctly outside Cursor Agent (e.g. other apps)
• Looks like numpad key events are being turned into Apple private-use “key symbol” codepoints instead of real characters
Hey, thanks for the detailed report. The exact codepoints you captured really helped us pinpoint the issue quickly.
What’s happening: the CLI enables enhanced keyboard mode in terminals that support it, and numpad keys come through as special key codes that the input box doesn’t currently translate back into digits and Enter. That’s why you see PUA glyphs instead of 1 2 3, and why numpad Enter doesn’t submit. This shouldn’t happen, and it’s not something in your setup. I’ve passed it to the team and we’re tracking it. I can’t share an ETA yet, but I’ll update the thread when there’s news.
For now, as a workaround, the top number row and the regular Enter work fine.
One quick question: which terminal are you running the CLI in, iTerm2, Ghostty, the built-in macOS Terminal, or WezTerm? This will help us make sure the fix covers your setup.
Thanks for the quick response. I am using iTerm on a macOS. The version of iTerm was 3.6.9 when i made the report. I’ve updated it to 3.6.11 just now, but (as expected) the same result.
