The official command reference, checked October 24, 2026, separates macOS, Windows, and Linux defaults. Some commands depend on the active feature or view. The table below concerns the desktop app; it is not a promise that a browser tab will handle the same keys.
Start with the commands you actually need
These defaults provide a small starting set:
| Action | Windows | macOS |
|---|---|---|
| Open command menu | Ctrl+Shift+P or Ctrl+K | Cmd+Shift+P or Cmd+K |
| Open settings | Ctrl+, | Cmd+, |
| Open keyboard shortcuts | Ctrl+/ | Cmd+/ |
| Start a new chat | Ctrl+N or Ctrl+Shift+O | Cmd+N or Cmd+Shift+O |
| Find text in the current chat | Ctrl+F | Cmd+F |
Choose one action to learn first. If you repeatedly reach for the mouse to find a phrase in the open conversation, practice Find in chat before memorizing navigation commands you rarely use.
Finding text in the current chat and searching across chats are different actions. The current desktop reference lists Search chats without a default binding; you can assign one in Keyboard Shortcuts. The chat-history search guide covers what to look for once you open that search.
Diagnose the command, the key, and the focus separately
Suppose you want to find a paragraph in the current conversation, but Ctrl+K opens a command menu. That matches the documented desktop default. Use Ctrl+F for the paragraph search instead of treating the command menu as a failed search box.
If a key still behaves unexpectedly:
- Open the command using its visible menu control. Check that you are looking for the right action.
- Find the action in Keyboard Shortcuts and inspect its current binding. Your configured binding may differ from a default table.
- Use keystroke search to see what the combination is assigned to.
- Return to the view where you want to use it, set focus there, and try again.
Focus matters. The official reference gives Ctrl+K or Cmd+K a terminal-clearing role when the terminal has focus. A command-menu shortcut and a terminal shortcut can therefore share keys while applying in different contexts. Check where the cursor is before changing a binding.
Change one binding and confirm its result
OpenAI's settings documentation describes editing bindings and resetting custom shortcuts to defaults. Change the relevant command rather than resetting all your preferences as a first step.
For a personal check, write a short record:
App and operating system: [ENTER]
Command wanted: [EXACT NAME]
Current binding: [WHAT SETTINGS SHOWS]
Active view and focus: [ENTER]
Observed result: [WHAT ACTUALLY OPENED OR CHANGED]
New binding, if changed: [ENTER]
Result after retry: [ENTER]
That record distinguishes “the command is unavailable here” from “this key runs another command.” If the command works through the menu but the key does nothing, keep both observations when requesting help. Include the app version and platform; omit conversation contents the recipient does not need.
Keep a small personal reference
Save only the shortcuts you use in your normal work, with their command names beside them. If a future update or another computer behaves differently, look up the command in that app's settings again. Recheck the changed shortcut in the view where you need it before adding another customization.