Change:
primary: KeyMod.CtrlCmd | KeyCode.Backspace, mac: { primary: KeyMod.Alt | KeyCode.Backspace } }); <ins> if (platform.isWindows) { // Delete word left: ctrl+h // Windows cmd.exe requires ^H to delete full word left registerSendSequenceKeybinding(String.fromCharCode('H'.charCodeAt(0) - 64), { when: ContextKeyExpr.equals(KEYBINDING_CONTEXT_TERMINAL_SHELL_TYPE_KEY, WindowsShellType.CommandPrompt), primary: KeyMod.CtrlCmd | KeyCode.Backspace, }); } </ins> // Delete word right: alt+d registerSendSequenceKeybinding('x1bd', { primary: KeyMod.CtrlCmd | KeyCode.Delete,

Discussion:
Within the integrated terminal using , I'd like to be able to use in order to delete an entire word, as can be done in the regular editor. does work inside powershell, but not when using . This is currently possible within the new Windows Terminal as well as the "old" Windows 10 terminal,
I'm still seeing deleting single characters in in the latest insiders. When usering powershell, I see ^W inserted after text on . The only terminal related setting I have set is and I don't have any other keybindings set for
I am unable to reproduce the deletion of single characters in or ^W in powershell. The behavior for powershell in particular seems strange -- I believe powershell accepts both and for deletion of an entire word. Your description of the behavior appears to be the same as that prior to ; however, and powershell seem flipped. I would think that it would be emitting ^W and powershell simply deleting a single character. Since was merged, I have been seeing the correct behavior in code-insiders. It is strange that your version seems to be without the change. Is still inserted for you after unfocusing and refocusing the terminal? Within the original pull request, In practice I do occasionally run into this. This should only ever affect -- I have never had it occur for either wsl2 or powershell. I am not sure if there is a good solution for this. The difficulty here is supporting both and WSL. It seems even does not correctly delete a whole word for WSL, though it does for and powershell. I suppose the issue here is more related to how keybindings are handled in that when there is a collision of bindings and one version is conditionally based on the currently focused shell, it requires one to unfocus the terminal for it to take effect.
I get this too. I see it both in powershell and in the python REPL running in powershell.
you might be on an older version of powershell? pwsh 7 works for me. For python, created
In Windows Terminal this works regardless of the backend, i.e. it works in python, CMD, whatever
I believe Windows Terminal sends actual keystrokes via the Windows native console API for these which would be handled correctly, whereas we want to avoid treating the communication with the underlying process on Windows specially.

does not work for me in either VS Code or VS Code insider integrated terminal "" I'd tried to override the default keybinding by but it produces output instead of deleting the word. ! By default, it simply deletes 1 character. Please help, it's unbearable to not being able to delete a whole word, should be a built-in behavior of any terminal tool, not sure why it has been marked "out of scope"
there is a default keybinding for cmd and it works fine for me: ! ! You may need to update Windows if it's not working for you?
just updated Windows (Version 10.0..3636), no more update to do -same issue (it works well in regular , but not in VSCode) however I see this suspicious output in the keybinding troubleshooting log -!