Claude Code Keyboard Shortcuts: The Ones Worth Learning (Desktop App and Terminal)

Claude Code keyboard shortcuts depend on where you run it. The desktop app has its own set, built around sessions and panes, and you can see all of them with Cmd+/ on macOS or Ctrl+/ on Windows. The terminal version has a different set, built around the prompt, and typing ? on an empty prompt shows them. In both, Esc stops Claude mid-response, which is the single shortcut I would learn before any other.

You do not need to memorize a cheat sheet. Most of the value is in about five keys per surface, and the rest you pick up when you need them. Below are the ones I would learn first, taken from Anthropic's own Claude Code docs, with the desktop app first because that is where I point most people starting out.

These apply to the Code tab in the Claude Code desktop app. On Windows, swap Cmd for Ctrl. Session cycling, the terminal toggle and the view mode toggle use Ctrl on both platforms.

My pick for the first week: Esc, Cmd+Shift+D and Cmd+Shift+M. Esc lets you stop Claude the moment it heads the wrong way instead of waiting for it to finish. The diff pane is where you review what changed before you trust it. And the permission mode menu is how you move between asking before every edit and letting Claude work, which permission modes explained covers in full.

The side chat (Cmd+;, or typing /btw) is the underrated one. It can read the main conversation up to that point, so you can ask a quick question without derailing the task Claude is in the middle of.

If you run Claude Code in a terminal or an editor's terminal, these are the ones I would learn first. Type ? on an empty prompt any time to see the full list.

The two I see beginners miss are Shift+Tab and Esc Esc. Shift+Tab is the fastest way into plan mode, which is where I start anything bigger than a small fix. Esc twice on an empty prompt opens the rewind menu, so a bad turn is not a disaster. Checkpoints and rewind explains what it can and cannot undo.

Shift+Enter works out of the box in iTerm2, WezTerm, Ghostty, Kitty, Warp, Apple Terminal and Windows Terminal, according to the docs. If it sends your prompt instead, use Ctrl+J, which works in any terminal, or type a backslash and then press Enter.

Three characters at the start of a prompt in the terminal do as much as any key combination:

In the terminal version, run /keybindings. It creates or opens ~/.claude/keybindings.json, and Claude Code picks up changes without a restart. The file is a list of blocks, each with a context (like Chat, Global or Transcript) and a map of keys to actions. Setting a key to null unbinds it. This example moves the external editor to Ctrl+E and frees up Ctrl+S:

{ "bindings": [ { "context": "Chat", "bindings": { "ctrl+e": "chat:externalEditor", "ctrl+s": null } } ] }

A few keys are reserved and cannot be rebound: Ctrl+C, Ctrl+D, Ctrl+M (always Enter), Ctrl+[ (always Escape), Ctrl+I (always Tab) and Ctrl+H. The basic text editing keys, like Ctrl+A, Ctrl+E, Ctrl+K and Ctrl+W in the prompt, also have no actions in the keybindings file, so you cannot remap them there.

If you would rather have Vim keys in the prompt, that is a separate setting: /config, then Editor mode. Claude Code with Vim and Neovim has the details.

My take: learn three, use them for a week, then add more. If you are in the desktop app, that is Esc, Cmd+Shift+D and Cmd+Shift+M. If you are in the terminal, it is Esc, Shift+Tab and Esc Esc. All of them are about control: stopping Claude, seeing what it changed and deciding how much it is allowed to do without asking. Speed shortcuts like model switching are nice later. Control shortcuts save you from bad edits on day one.

If you are new to all of this, start in the desktop app, where the shortcuts list is one key away and the panes do a lot of the work for you. Claude Code tips for beginners and Claude Code day one setup cover the rest of the first hour.