there's some new windows-originated keyboard protocol because of course there is

[dankamongmen]

saw a reference to this over in kovidgoyal/kitty#3248 (comment) ... https://github.com/microsoft/terminal/blob/main/doc/specs/%234999%20-%20Improved%20keyboard%20handling%20in%20Conpty.md (that's the real uri jfc msft) Improved Keyboard Handling in ConPTY

[unxed]

There are at least two more:

1. iTerm2 "raw keyboard" protocol:
   https://gitlab.com/gnachman/iterm2/-/issues/7440#note_129307021

But iTerm2 also supports kitty keyboard protocol now, so I am not sure that implementing iTerm2's own protocol worth trying.

2. far2l extensions — one more protocol capable of sending detailed key events information, stored in form close to win32-input-mode, but encoded differently. It also supports clipboard interaction and some other useful things.

cyd01/KiTTY#74 (comment)
https://github.com/elfmz/far2l/blob/master/WinPort/FarTTY.h

This protocol is already supported in
— KiTTY by cyd01, advanced fork of PuTTY
— putty-ng, advanced fork of PuTTY
— Modern Turbo Vision port by magiblot
— Text editor "turbo" by magiblot
— far2l file manager (and it's internal internal virtual)

[j4james]

FYI, you've already got an issue for this "new" keyboard protocol (see #2770), which was developed 5 years ago, 8 months earlier than the kitty keyboard protocol that you're currently using.