Claude Code shortcuts worth memorising: stop early, go back, run in background
TL;DR
Esc to interrupt, Esc Esc to go back, Shift+Tab to change permission mode, Ctrl+B to background, Ctrl+G for long prompts in your editor, ! for shell commands. Knowing these means stopping wrong directions sooner and spending fewer tokens.
Many people use Claude Code daily but only know how to type a prompt and press Enter. Yet a few shortcuts and input prefixes let you interrupt Claude at the right moment, go back to an earlier point, push long commands to the background, or write long prompts in your usual editor. These are the ones most worth memorising, drawn from the official interactive mode docs.
Session control
| Key | What it does |
|---|---|
Esc | Interrupt Claude mid-turn to redirect; work done so far is kept |
Esc Esc | With text: clear the draft (Up arrow brings it back). Empty prompt: open the rewind menu |
Shift+Tab | Cycle permission modes (Manual, acceptEdits, plan…) |
Ctrl+C | Interrupt; when idle, clear the input, press again to exit |
Ctrl+B | Background a running Bash command or agent |
Ctrl+O | Open the detailed transcript: tools called, model for each reply |
Ctrl+T | Show/hide Claude's to-do checklist |
Ctrl+L | Redraw the screen when the display is garbled |
Writing prompts
| Key | What it does |
|---|---|
Ctrl+G | Open the prompt in your default editor, good for long prompts |
Ctrl+V | Paste an image from the clipboard (inserts an [Image #N] chip); iTerm2 uses Cmd+V |
Ctrl+R | Reverse-search your prompt history |
Ctrl+S | Stash the prompt you're writing; press again on an empty prompt to restore it |
Ctrl+U | Delete from the cursor to the start of the line |
Line prefixes
/: invoke a command or skill.!: shell mode, runs a command directly and adds its output to the session for Claude to respond to. For example! git status.@: file path autocomplete to mention files in your prompt.
Sending more while Claude works
You can keep typing while Claude is running; messages are queued and delivered at a suitable point instead of you having to interrupt. Use it to add details without breaking the flow.
Caveats
- Shortcuts vary by terminal: Option/Alt shortcuts on macOS require configuring Option as Meta in your terminal.
- They're customisable: remap keys in
~/.claude/keybindings.jsonif they clash with your terminal or tmux. - Vim mode: a vim-style editing mode exists for those who prefer it; enable it in config.
How to apply it
- Dev: Practise
Esc,Esc EscandCtrl+Bfor a week; they save the most tokens because they let you stop early and go back to the right point. - Tech Lead: Print this shortcut table for your team's Claude Code onboarding.
- PM: Use
Ctrl+Vto paste a screenshot of the bug instead of describing it in words.
Sources & references
- Interactive mode — Claude Code Docs