[BUG] Detect fixterm representations or Detect KKP

[rhodes-b]

Environment

• Platform (select one): unknown - im reporting this on behalf of a ghostty user
• Terminal: Ghostty

Bug Description

claude code does not recognize fixterm key encodings and spits the fixterm encoding into the input box this is very unintuitve for users

Steps to Reproduce

Use ghostty and use a keybind with a modifier so it will have a fixterm representation (ghostty uses fixterm by default users have to override the keybind manually) shift + enter to do a newline in the prompt is a easy way to achieve this

Expected Behavior

newline in prompt

Actual Behavior

fixterm encoding is thrown into input box

Additional Context

https://www.leonerd.org.uk/hacks/fixterms/

Kitty keyboard protocol support would also solve this problem https://sw.kovidgoyal.net/kitty/keyboard-protocol/

[github-actions[bot]]

Found 2 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/1282
2. https://github.com/anthropics/claude-code/issues/5757

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

[rhodes-b]

Yup I found the duplicate, very surprising its just been sitting for months. I dont know what /terminal-setup does but you can detect KKP https://sw.kovidgoyal.net/kitty/keyboard-protocol/#detection-of-support-for-this-protocol

which should absolutely not require some hacky command users just have to know to run

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[pzmarzly]

still an issue