Warp Keyboard Shortcuts

What's in this Warp cheat sheet

Over 100 verified default shortcuts per platform, grouped the way you actually use them. Warp is a terminal, so the interesting bindings are not the copy-and-paste ones — they are blocks (Warp's unit of command plus output), panes, the command palette, and the surprisingly deep input editor, which supports Emacs-style motion, multiple cursors and code folding on the command line.

Use the platform tabs below to switch between macOS and Windows/Linux, and the search box to jump to a key or an action name. Every row also lists Warp's internal action identifier where it is useful, because that is the exact string you need when writing a custom keybindings.yaml.

The one thing to know first

Warp's macOS keyset and its Windows/Linux keyset are genuinely different, not just Cmd swapped for Ctrl. Most Mac ⌘ bindings become Ctrl+Shift on Windows and Linux, and several actions that have a default on macOS ship unbound on Windows and Linux — the launch configuration palette, the theme picker, the navigation palette and all four pane-resize commands among them. Those are marked below so you know to assign them yourself rather than hunt for a key that does not exist. Windows and Linux share one identical keyset.

Warp Agent Mode shortcuts (September 2026)

Last verified 2 September 2026 against Warp's keyboard shortcuts reference and the Terminal and Agent modes docs. Warp is now an agentic terminal: Cmd+Enter (Mac) or Ctrl+Shift+Enter (Windows/Linux) starts a new agent conversation from the prompt — the same as typing /agent. Option+Cmd+Enter / Ctrl+Alt+Enter starts a cloud agent. Esc returns you to the terminal. In conversation view, press ? to show the in-app shortcut panel.

On Windows and Linux, Ctrl+Shift+Enter is also the default for maximize pane, and Ctrl+Shift+I is both Agent auto-accept and “reinput selected command.” If one chord does the wrong thing, remap it. Ctrl+I is Warpify Subshell and the Agent/shell toggle on Windows and Linux — remap if they collide. Pair this page with Claude Code shortcuts and OpenCode shortcuts if you run those agents inside Warp.

A note on the Meta key

Warp documents a number of input editor bindings against Meta. On most keyboards this is Option on macOS and Alt on Windows and Linux, but it depends on how your terminal and OS map the modifier. If a Meta binding such as Meta+. (insert the last word of the previous command) does nothing, check whether your Option or Alt key is configured to send Meta rather than composing accented characters.

Customize Warp keyboard shortcuts

There are two routes, and they stay in sync — anything you change in the UI is written back to the file.

1. In the app

Open Settings > Keyboard shortcuts (Ctrl+⌘+K on macOS opens the keybindings editor directly). Search by action name or by the existing key, then set, clear, or reset to default. Bindings that clash with another binding are flagged with an orange border, so a conflict is visible before you save.

2. In keybindings.yaml

For version-controlled or scripted setups, Warp reads ~/.warp/keybindings.yaml. It is a flat YAML map of action name to key string. Create the ~/.warp directory first if it does not exist, then restart Warp to pick up changes.

# ~/.warp/keybindings.yaml
workspace:toggle_command_palette: cmd-p
pane_group:add_right: cmd-d
pane_group:add_down: cmd-shift-D
terminal:clear_blocks: cmd-k
editor_view:move_to_line_start: ctrl-a
workspace:show_command_search: ctrl-r

Two rules catch people out. Modifiers are hyphen-separated and lowercase, ending with the key — cmd-ctrl-g, not Cmd+Ctrl+G. And when a binding includes Shift, the letter must be capitalised: cmd-shift-A is Command+Shift+A, while cmd-a is plain Command+A.

Non-printing keys use descriptive names: up, down, left, right, home, end, pageup, pagedown, backspace, enter, insert, delete, escape, tab, numpadenter, and f1 through f20.

3. Import a preset keyset

Warp maintains ready-made presets in the warpdotdev/keysets repository — useful if you are migrating muscle memory from another terminal. Back up any existing keybindings.yaml, copy the preset in, rename it to keybindings.yaml, and restart Warp. To revert, delete the file and restore your backup.

Why your Warp shortcuts stopped working

Four causes account for nearly every report, and only the first is in Warp's own documentation.

macOS is intercepting the key

System-level shortcuts including ⌘+Esc, ⌘+`, ⌘+Tab, ⌘+. and ⌘+~ are claimed by macOS before Warp ever sees them. Unbind them in System Settings first, then assign them in Warp.

You switched to a non-Latin keyboard layout

This is the one that catches people and has no fix in the docs. If you change your input source to something like Persian, Arabic, Russian or Greek, bindings such as copy and paste silently stop firing. Warp does not currently convert input from sources other than ABC, so the workaround is to rebind the keys from scratch while the new input source is active. It is tracked as a known issue on Warp's GitHub.

A full-screen program has the keys

While a long-running or full-screen command is in the foreground — think vim, less, htop — Warp forwards PageUp, PageDown, Home and End straight to that program instead of scrolling the terminal. This is intended behaviour, not a bug.

Two bindings are fighting

Open Settings > Keyboard shortcuts and look for the orange border. Warp highlights conflicting bindings rather than silently picking a winner.

Vim keybindings in the input editor

Warp can run the command input in Vim mode. Turn it on under Settings > Features > Editor with Edit commands with Vim keybindings. It remains a beta feature, and one limitation is worth knowing before you commit to it: the built-in Vim bindings themselves cannot currently be remapped, though the request is open with the Warp team.