Codex Desktop on Windows 10: Ctrl+Shift+V pastes clipboard content twice

Resolved 💬 1 comment Opened Jun 9, 2026 by fibsion-Pm Closed Jun 10, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.602.71036

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

In Codex Desktop on Windows 10, pressing Ctrl+Shift+V in the chat input area pastes the current clipboard content twice.

This appears to conflict with the default shortcut shown in Codex settings, where Ctrl+Shift+V is assigned to "Start or stop voice mode".

Actual behavior:

  1. The clipboard content is inserted twice into the Codex chat input area.
  2. This happens after pressing Ctrl+Shift+V only once.

Impact:
This disrupts normal input, especially when pasting long prompts, commands, logs, or code snippets.

What steps can reproduce the bug?

Feedback ID: 019d8bde-5306-7ad1-ab2c-5cbc52f62271

Reproduction steps:

  1. Open Codex Desktop on Windows 10.
  2. Focus the chat input area.
  3. Copy any plain text to the clipboard, for example: test
  4. Press Ctrl+Shift+V once.
  5. Observe that the clipboard text is pasted twice into the chat input.

Additional note:
In Codex settings, Ctrl+Shift+V is shown as the shortcut for "Start or stop voice mode".

What is the expected behavior?

Pressing Ctrl+Shift+V once in the Codex chat input area should not paste the clipboard content twice.

Expected result:

  1. The text should be pasted only once; or
  2. If Ctrl+Shift+V is intended for voice mode, it should not also trigger duplicate paste behavior in the chat input.

Additional information

Since Ctrl+Shift+V is commonly used for paste or paste-without-formatting in many applications, please consider changing the default shortcut for "Start or stop voice mode" to a less conflicting shortcut.

A short screen recording or screenshot of the shortcut setting can be provided if helpful.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗