Modifier keys behave incorrectly in VS Code + WSL terminal when chatting with Codex
Open 💬 1 comment Opened Mar 17, 2026 by jasonrale
What version of Codex CLI is running?
codex-cli 0.115.0
What subscription do you have?
plus
Which model were you using?
_No response_
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
VSCode
What issue are you seeing?
CapsLock and Shift behave incorrectly in VS Code + WSL terminal when chatting with Codex
- Windows 11
- VS Code
- WSL Ubuntu via VS Code
- Terminal chat with Codex
This issue currently only appears in this environment.
What steps can reproduce the bug?
- Open VS Code on Windows 11
- Connect to WSL Ubuntu
- Open the integrated terminal
- Start chatting with Codex
- Try:
- CapsLock off + letter
- CapsLock off + Shift + letter
- CapsLock on + letter
- CapsLock on + Shift + letter
What is the expected behavior?
### Expected behavior
- With CapsLock on, pressing a letter should input uppercase
- With CapsLock off, pressing Shift + letter should input uppercase
- Shift + Enter should insert a newline normally
### Actual behavior
- With CapsLock off, Shift + letter does not produce uppercase
- With CapsLock on, pressing a letter still does not produce uppercase
- Uppercase only works when CapsLock is on and Shift + letter is pressed
Additional information
There is also a low-probability variant where uppercase input works normally, but Shift + Enter stops working, so multiline input is not possible. This is not reproducible reliably yet, but it may be related to the same modifier-key handling issue.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗