[Bug] AltGr characters not typed in chat input on Windows with German keyboard layout

Bug Description
Title: [BUG] Regression: AltGr characters [ ] ~ cannot be typed in chat input on native Windows (German layout) ## Environment - Claude Code: 2.1.292 - OS: Windows 11 Pro 10.0.26200 (native, not WSL) - Terminal: Windows Terminal Preview (scoop install), PowerShell 7 profile - Keyboard layout: German (QWERTZ) ## Bug Typing [ (AltGr+8), ] (AltGr+9) and ~ (AltGr++) into the Claude Code chat input produces nothing. The keystrokes are silently dropped. ## Expected The characters are inserted into the input, as they are in any other console application. ## What works / what was ruled out - The same keystrokes work in a plain PowerShell (PSReadLine) prompt in another tab of the same Windows Terminal window. - Pasting []~ into the Claude Code input works. - Toggling Windows Terminal's altGrAliasing (false → true, new tab) makes no difference. - No custom ~/.claude/keybindings.json is present. - Not keyboard-specific: the keyboard sends standard RAlt+key (AltGr), which every other app interprets correctly. ## Likely cause On Windows, AltGr is synthesised as LCtrl+RAlt. Claude Code's input layer appears to treat the chord as a Ctrl/Alt key combination instead of inserting the OS-composed character. ## Related issues - #72021 – same symptoms on native Windows 11 / Windows Terminal, closed as fixed on 2026-07-05 (reported on 2.1.178). This looks like a regression of that fix. - #59045 – AltGr+plus (]) intercepted on Windows, Italian layout; keybindings.json null overrides did not help. - #67380 – earlier AltGr regression on WSL2 (2.1.172). ## Impact Brackets and tilde are essential for writing code and paths. Currently the only workaround is copy-pasting each character.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.292
• Feedback ID: 9501dd72-79ef-490e-ab98-fbd3a76b77f2