Windows terminals using win32 input mode now deliver function keys and modifiers correctly.
What's wrong with this entry?
Claude 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.
- The input parser now carries a high-surrogate field across chunks so emoji and other surrogate pairs split across reads are reassembled.
- The terminal private-mode table gained
WIN32_INPUT_MODE: 9001, and its enable/disable sequence constants moved out of lazy module init.
win32HighSurrogate, WIN32_INPUT_MODE: 9001,
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window