Claude Code lives in the terminal, which means everything you do is a keystroke. The built-in shortcuts are not flashy, but they make a daily difference. Here is the full set, grouped by what you actually use them for.
Sending and Editing Messages
Enter— Send the current message.Shift + Enter— Insert a newline without sending. Use for multi-line prompts or pasting code blocks.\+ Enter` — Alternative newline (works in terminals where Shift+Enter is intercepted).Esc— Stop Claude mid-response. The single most important shortcut. Use it the moment you see Claude going down the wrong path.Esc Esc(double-tap) — Open the message history picker; pick any earlier message and edit it to fork the conversation.Ctrl + C— Cancel the current input or interrupt a tool call.Ctrl + D— Exit Claude Code.Ctrl + L— Clear the visible terminal (does not clear conversation memory; use/clearfor that).
Modes
Shift + Tab— Cycle through modes: default, auto-accept edits, plan mode.- Default: Claude asks before edits and tool calls.
- Auto-accept: Claude applies edits without asking. Fast but trusting.
- Plan mode: Claude can read but not write. It produces a plan and waits for approval before executing.
!at the start of an input — Drop into a one-shot bash command. Output is added to context.#at the start of an input — Add a memory entry toCLAUDE.md.@— Reference a file. Tab-completion lists files in the working directory; the contents are pulled into context.
Queueing and Multi-Tasking
- Type while Claude is working — Your input is queued and processed when the current turn ends. You do not have to wait for Claude to finish before drafting the next instruction.
Up Arrow/Down Arrow— Cycle through your previous prompts (shell-style history).
Pasting Images
Ctrl + V— Paste an image from the clipboard directly into the prompt. Works for screenshots, diagrams, mockups. Claude reads them as part of the message.
Vim Mode
If you prefer modal editing inside the prompt, enable vim mode in /config or via --vim. You get the usual i, Esc, dd, yy, /search, etc. — minus the Helix bindings, which are not currently supported.
Tips That Compound
- Esc is your steering wheel. The instinct to let Claude finish a wrong response is the single biggest time waster. Hit Esc, redirect, continue.
- Plan mode for risky changes. Toggle with Shift+Tab before asking for migrations, refactors, or anything destructive. Approve the plan, then let it execute.
@over copy-paste. Referencing a file with@path/to/fileis always cleaner than pasting its contents — Claude can read it in one tool call and you keep your input short.- Queue ahead. While Claude runs tests, type the next instruction. By the time the run finishes, your follow-up is ready.
The shortcuts are simple. The fluency takes a week. After that, reaching for the mouse feels wrong.