See the live list
Run /hotkeys from any session to dump the chords as the current build sees them. That list reflects active remaps and any chords added by plugins; the tables below are the out-of-the-box defaults.
Editor — navigation
| Key | Action | …
Editor — editing
| Key | Action | …
On Windows Terminal, Ctrl+Enter never reaches the app — use the Ctrl+Q follow-up chord there; Shift+Enter is indistinguishable from Enter and lands as steering.
Editor — control
| Key | Action | …
Models
| Key | Action | …
Dashboards (navigator surfaces)
/tree, /extensions, and /agents share a common navigator. Escape closes; an active filter gets cleared by the first Escape and the second exits.
| Key | Action | …
Pickers
File and history pickers (@ file references, prompt search, the prompt-actions menu on #) share their motion keys with the editor: Up/Down walk the list, Tab accepts the highlight, Escape dismisses. The @ picker fuzzy-matches every file under the project root not ignored by .gitignore.
Plan mode chords
| Key | Action | …
Customize
Remaps live in ~/.omp/agent/keybindings.yml — a separate file from config.yml. Each entry maps a namespaced action ID (as printed by /hotkeys, e.g. app.model.cycleForward, tui.editor.undo) to a chord, or to an array of chords if you want more than one to fire the action. Chord notation matches what /hotkeys prints in canonical form: lowercase, +-joined, e.g. ctrl+p, alt+shift+p, alt+up. See Settings for where the agent directory lives, and Slash commands for the commands the chords trigger.
…
> Legacy short names from older configs (`cycleModelForward`, `togglePlanMode`, …) are auto-migrated to the namespaced form on load; a legacy `keybindings.json` is migrated to `keybindings.yml` (`keybindings.yaml` is also accepted).
> Action names are stable across releases; if a chord stops working after upgrading, run `/hotkeys` and compare to your map.\n
[…49ln elided; re-read needed ranges, e.g. /home/usr/funday/dev/docs/content/omp/keybindings.md:19-23,28-38]