Ë Bjœ ãó$—dZddlmZdd„Zdd„Zy)u½Augmentations to prompt_toolkit's input-parsing tables. Imported once at CLI startup. Each helper installs a small mapping into prompt_toolkit's `ANSI_SEQUENCES` so byte sequences emitted by modern keyboard protocols (Kitty / xterm `modifyOtherKeys`) decode to existing key tuples Hermes already binds. Kept in a standalone module — separate from `cli.py` — so the registrations can be unit-tested without importing the whole CLI runtime. é)Ú annotationscó¾— ddlm}ddlm}|j |j f}d}dD]!}|j|«|k7sŒ|||<|dz }Œ#|S#t$rYywxYw)uÃMap Shift+Enter byte sequences to the (Escape, ControlM) key tuple that Alt+Enter produces, so the existing Alt+Enter newline handler fires for terminals that emit a distinct Shift+Enter. Sequences mapped: - "\x1b[13;2u" — Kitty keyboard protocol / CSI-u, modifier=2 (Shift) - "\x1b[27;2;13~" — xterm modifyOtherKeys=2, modifier=2 (Shift) - "\x1b[27;2;13u" — alternate ordering some emitters use The CSI-u sequence is not in stock prompt_toolkit. The modifyOtherKeys variant `\x1b[27;2;13~` IS in stock prompt_toolkit but mapped to plain `Keys.ControlM` — i.e. Shift+Enter behaves identically to Enter, which is the very bug this helper exists to fix. We therefore overwrite those two specific keys (and `\x1b[27;2;13u`) unconditionally; other `\x1b[27;...;13~` sequences (Ctrl+Enter, Alt+Enter via modifyOtherKeys variants 5/6/etc.) are left untouched. Default macOS Terminal and stock Windows Terminal still send the same byte for Enter and Shift+Enter, so there is no fix for those terminals at the application layer — the sequences above never reach Hermes. Returns the number of sequences whose mapping was changed. r©ÚANSI_SEQUENCES©ÚKeys)zz [27;2;13~z é©Ú*prompt_toolkit.input.ansi_escape_sequencesrÚprompt_toolkit.keysrÚ ExceptionÚEscapeÚControlMÚget©rrÚ alt_enterÚchangedÚseqs ú?/home/ubuntu/.hermes/hermes-agent/hermes_cli/pt_input_extras.pyÚinstall_shift_enter_aliasrsv€ð0ÝMÝ,𗑘dŸm™mÐ,€IØ€GØ?òˆØ × Ñ ˜cÓ " iÓ /Ø"+ˆN˜3Ñ Ø q‰L‰Gðð €Nøô òÙðúó‚ AÁ AÁAcó¾— ddlm}ddlm}|j |j f}d}dD]!}|j|«|k7sŒ|||<|dz }Œ#|S#t$rYywxYw)uMap Ctrl+Enter byte sequences to the (Escape, ControlM) key tuple that Alt+Enter produces, so the existing Alt+Enter newline handler fires for terminals that emit a distinct Ctrl+Enter. Sequences mapped: - "\x1b[13;5u" — Kitty keyboard protocol / CSI-u, modifier=5 (Ctrl) - "\x1b[27;5;13~" — xterm modifyOtherKeys=2, modifier=5 (Ctrl) - "\x1b[27;5;13u" — alternate ordering some emitters use Stock prompt_toolkit doesn't map any of these. Without this alias, Kitty/mintty/xterm-with-modifyOtherKeys users over SSH never get a Ctrl+Enter newline — the keystroke arrives as a raw CSI sequence that falls through to the default character-insert handler. See #22379. Returns the number of sequences whose mapping was changed. rrr)zz [27;5;13~z r r rs rÚinstall_ctrl_enter_aliasr6sv€ð"ÝMÝ,𗑘dŸm™mÐ,€IØ€GØ?òˆØ × Ñ ˜cÓ " iÓ /Ø"+ˆN˜3Ñ Ø q‰L‰Gðð €Nøô òÙðúrN)ÚreturnÚint)Ú__doc__Ú __future__rrr©órúr sðñ õ#ó$ôNr