Ctrl-F is hard-bound to Find/Search in Codex Desktop, blocking Emacs-style navigation

Resolved 💬 1 comment Opened Apr 10, 2026 by qwertyerge Closed Apr 10, 2026

Title: Ctrl-F is hard-bound to Find/Search, preventing Emacs-style text navigation in Codex Desktop

In Codex Desktop on macOS, Ctrl-F is reserved for Find/Search. In text editing contexts, this prevents the common Emacs-style meaning of Ctrl-F (forward-char).

Expected behavior:

  • Text input areas should support configurable keybindings, or provide a built-in Emacs-style keymap.
  • At minimum, Ctrl-F should be rebindable in composer/thread text fields.

Actual behavior:

  • Ctrl-F triggers Find/Search instead of moving the cursor forward by one character.
  • No obvious keybinding customization path is available.

Impact:

  • This reduces editing efficiency for users who rely on standard Emacs-style cursor movement in text inputs.
  • The issue likely extends to related navigation bindings such as Ctrl-B, Ctrl-A, and Ctrl-E.

Request:
Please add customizable keyboard shortcuts, or an Emacs keybinding mode for text editing in Codex Desktop.

Environment:
Codex Desktop for macOS

View original on GitHub ↗

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