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

Resolved 💬 4 comments Opened Apr 8, 2026 by erinok Closed Jun 12, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

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

#16103
#15831
#15739

Powered by Codex Action

kurochan · 4 months ago

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.

0xdevalias · 2 months ago

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.

@kurochan You should be able to change the default keybinding in 'Settings -> Keyboard Shortcuts -> Find'.

You could also manually edit ~/.codex/keybindings.json (which editing via the UI would do for you anyway I believe)

The defaults seem to use CmdOrCtrl+F / similar; whereas I believe you can just use Command+F. You can also configure multiple bindings this way.

Some basic examples from mine (note that this is for the global search, not the find search specifically):

[
  // ..snip..
  {
    "command": "searchChats",
    "key": "CmdOrCtrl+Shift+F"
  },
  {
    "command": "searchChats",
    "key": "CmdOrCtrl+G"
  },
  // ..snip..
]

I just tested editing from the UI, and the key you want seems to be findInThread:

[
  // ..snip..
  {
    "command": "findInThread",
    "key": "Command+F"
  },
  // ..snip..
]

---

Edit: Update regarding multiple keybindings: Codex accepts and displays multiple bindings for one command, but some commands implemented through the native application menu currently activate only the first configured entry. Reordering the entries changes which shortcut works, so put the preferred shortcut first for now. I reported that runtime bug in:

#27834

The settings UI can also append another binding, but this is exposed through a difficult-to-discover Shift-click gesture on the shortcut edit button; see:

#27835

erinok · 2 months ago

thx for the comment 0xdevalias -- actually this is fixed by default in latest codex, so i'll close issue.