Cmd. /keymap
Inspect and remap TUI keyboard shortcuts.
Key takeaways
- Inspect and remap TUI keyboard shortcuts.
- Check the input surface and availability before using the examples below.
Purpose
Inspect and remap TUI keyboard shortcuts.
/keymapAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/keymapWhen to use it
- Use
/keymapwhen tmux, SSH, VS Code terminal, or JetBrains terminal conflicts with default bindings. - Use
/keymap debugto inspect terminal key events when the changelog-supported debug flow is available. - Review Vim composer contexts before standardizing modal editing shortcuts.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/keymap | Remaps shortcuts | Input or navigation shortcuts conflict |
/statusline | Changes footer items | Visibility fields need adjustment |
/title | Changes terminal title items | Window identification needs adjustment |
Effects and persistence
Shows the current keyboard shortcuts and input configuration.
/keymap edits TUI shortcut bindings by context and action, then persists custom bindings to
tui.keymap in config.toml.
Cautions
- Key names and contexts can expand by CLI version; document values observed in the UI.
- Avoid forcing personal preferences as team defaults unless they solve a real conflict.
Official sources
Complete command list · Verification scope · History for this command