-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Closed
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
What version of Codex is running?
v0.50.0
What subscription do you have?
Plus
Which model were you using?
gpt-5-codex high
What platform is your computer?
Microsoft Windows NT 10.0.20348.0 x64
What issue are you seeing?
Summary
Pasting text into the Codex CLI prompt sometimes drops the lowercase “i” character.
Example: pasting “Metrics” renders as “Metrcs”.
Environment
- OS: Windows 11 [build/version]
- Shell host: PowerShell [5.x/7.x] (also tried: cmd.exe, Windows Terminal)
- Codex CLI version: [output of
codex --version] - Install method: [npm -g / GitHub release / Homebrew]
- Running under: [native Windows / WSL / Remote-SSH etc.]
Steps to Reproduce
- Launch Codex CLI on Windows (
PowerShell → codex). - Copy the string Metrics from Notepad.
- Paste into the Codex prompt with Ctrl+V.
Expected Result
The prompt shows Metrics.
Actual Result
The prompt shows Metrcs (lowercase “i” missing).
Evidence
- Clipboard bytes confirm “i” is present:
powershell -NoProfile -Command "[System.Text.Encoding]::Unicode.GetBytes((Get-Clipboard -Raw)) | Format-Hex"
Output includes:4D 00 65 00 74 00 72 00 69 00 63 00 73 00. - Typing the missing “i” manually works.
- Reproducible on Windows 11 (PowerShell 5/7). Not observed in plain cmd.exe or PowerShell outside Codex.
Additional Diagnostics
- Verbose logs: [attach if available; see notes below]
- Keyboard layout / IME: [e.g., Turkish Q / US-International etc.]
- Terminal: [PowerShell console / Windows Terminal tab]
- Does it repro under WSL with
codex? [Yes/No]
Workarounds
- Manually type the missing “i” after paste.
- Paste into another editor first, then copy/paste into Codex.
What steps can reproduce the bug?
Steps to Reproduce
- Launch Codex CLI on Windows (
PowerShell → codex). - Copy the string Metrics from Notepad.
- Paste into the Codex prompt with Ctrl+V.
What is the expected behavior?
Expected Result
The prompt shows Metrics.
Additional information
Evidence
- Clipboard bytes confirm “i” is present:
powershell -NoProfile -Command "[System.Text.Encoding]::Unicode.GetBytes((Get-Clipboard -Raw)) | Format-Hex"
Output includes:4D 00 65 00 74 00 72 00 69 00 63 00 73 00. - Typing the missing “i” manually works.
- Reproducible on Windows 11 (PowerShell 5/7). Not observed in plain cmd.exe or PowerShell outside Codex.
Additional Diagnostics
- Verbose logs: [attach if available; see notes below]
- Keyboard layout / IME: [e.g., Turkish Q / US-International etc.]
- Terminal: [PowerShell console / Windows Terminal tab]
- Does it repro under WSL with
codex? [Yes/No]
Workarounds
- Manually type the missing “i” after paste.
- Paste into another editor first, then copy/paste into Codex.
Metadata
Metadata
Assignees
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems