{"version":"2.1.248","anchor":"windows-terminal-input-sequences-are-now-decoded","canonical_anchor":"windows-terminal-input-sequences-are-now-decoded","heading":"Windows terminal input sequences are now decoded","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/windows-terminal-input-sequences-are-now-decoded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Windows terminal input sequences are now decoded\n\nWindows terminals using win32 input mode now deliver function keys and modifiers correctly.\n\n**What**\n\nClaude Code can decode win32 input-mode key sequences (ESC [ params _) that some Windows terminals emit, turning them into normal key input including function keys, ctrl\/alt modifiers and repeat counts.\n\n**Details**\n\n- The input parser now carries a high-surrogate field across chunks so emoji and other surrogate pairs split across reads are reassembled.\n- The terminal private-mode table gained `WIN32_INPUT_MODE: 9001`, and its enable\/disable sequence constants moved out of lazy module init.\n\n**Evidence**\n\n`win32HighSurrogate`, `WIN32_INPUT_MODE: 9001,`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}