openai / openai/codex

Keyboard shortcut conflict / accessibility / international text input bug.

Open
#46,280 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

ChatGPT Powered by Codex & OWL Version 26.908.70816 Released 14 sept 2026

What subscription do you have?

20 usd/month

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Bug report: Alt numeric codes are intercepted by the ChatGPT/Codex desktop interface.

What steps can reproduce the bug?

I use an English physical keyboard on Windows using Windows Alt numeric codes to type Spanish characters, e.g. Alt+162 for ó, Alt+164 for ñ, etc.
When the text input box is focused in the Codex/ChatGPT desktop app, pressing Alt+number is captured by the app as a shortcut and navigates to another chat instead of allowing Windows to input the character.

What is the expected behavior?

When focus is inside the message composer/text box, Alt+numpad numeric codes should be passed through to Windows text input, or there should be an option to disable Alt+number chat navigation shortcuts.
Actual behavior:
Alt+number changes/navigates chats and prevents typing Spanish characters with Windows Alt codes.

Additional information

In brief:
keyboard shortcut conflict / accessibility / international text input bug.
Environment:
Windows, English keyboard layout, ChatGPT/Codex desktop app.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Windows desktop app with the message composer focused, using Alt+162 and Alt+164, and confirm whether chat navigation is triggered. Done means Alt+numpad input reaches Windows text entry while composing, or a clearly documented option disables the conflicting Alt+number shortcuts.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.