Control-F shortcut for find conflicts with system binding for "move forward one character"

[erinok]

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

Version 26.325.31654 (1272)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

On macOS, Control-F (Control-B etc) are standard "emacs-style" text movement shortcuts -- but Codex overrides Control-F to open the search box. (This is redundent and undesired on macOS because Command-F is already bound to the search bar shortcut.)

What steps can reproduce the bug?

In a text entry box, type Control-F. The find dialogue opens.

What is the expected behavior?

Insertion point moves one character to the right.

Additional information

No response

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Incorrect Shortcut Binding of ⌃F #16103
• macOS: Ctrl+F is globally bound to Search and interrupts text input (expected “move forward one character”) #15831
• misbind Ctrl+F on macos #15739

Powered by Codex Action

[kurochan]

This looks like a duplicate at first glance, but I’m still seeing it on the current build, so it seems like the issue has regressed.
Ctrl-F still opens find instead of moving forward one character in text inputs on macOS.