Skip to content

Keyboard

Shortcuts

Everyone learns Esc. These are the rest — all checked against Claude Code itself, not copied off a blog.

The three to learn first

If you remember nothing else.

  • Esc Esc
    Stop Claude mid-action The moment Claude starts doing something you did not intend.
  • Esc thenEsc Esc thenEsc
    Clear the input box Your half-written prompt has turned into a mess and you want a clean line.
  • Shift +Tab Shift +Tab
    Cycle permission mode Starting an exploration (plan) or letting an agreed plan run (accept edits). On older Windows setups without VT mode, this is Meta+M instead.

Writing the prompt

Composing, searching, pasting.

  • Ctrl +J Ctrl +J
    Start a new line without sending Any prompt longer than one sentence.
  • Ctrl +R Ctrl +R
    Search your prompt history "What did I type last week that worked?" Inside the search, Ctrl+S cycles the scope: this session → this project → everywhere.
  • Ctrl +S Ctrl +S
    Park the half-written prompt You are three sentences into a prompt and need to go check something.
  • Ctrl +G Ctrl +G
    Edit the prompt in your real editor Writing anything long or carefully structured.
  • Ctrl +V Alt +V
    Paste an image Anything visual. Annotate the screenshot first and it works even better. Ctrl+V, not Cmd+V — macOS keeps Cmd+V for its own paste. Windows and WSL use Alt+V. On WSL both Ctrl+V and Alt+V work.
  • Option +T Alt +T
    Toggle thinking for the next turn One hard question in the middle of otherwise simple work.
  • Ctrl +_ Ctrl +_
    Undo in the input box You deleted half a prompt by accident.

Seeing what happened

What Claude did and what it plans to do.

  • Ctrl +O Ctrl +O
    Toggle the full transcript You want to know what it actually did, not the summary.
  • Ctrl +T Ctrl +T
    Toggle the task checklist Any multi-step task, before it gets far.

Running the session

Long jobs, models, the terminal.

  • Ctrl +B Ctrl +B
    Send the running job to the background A long build, test run, or search you do not want to sit and watch.
  • Option +P Alt +P
    Switch model Between tasks — rarely a good idea mid-task.
  • Option +O Alt +O
    Toggle fast mode Straightforward work where you would rather have speed than depth.
  • Ctrl +Z Ctrl +Z
    Step out to the shell without quitting You need the terminal for one command and do not want to lose the session. Terminal-level shortcut (Unix SIGTSTP), not a Claude Code binding. Windows has no direct equivalent.

The keys are the same on both systems — only the modifier's name changes (macOS calls Alt Option). Run /keybindings in any session to see exactly what is bound on your machine.

Drop the persona — "You are a senior engineer…" adds nothing

← Tips Prompting

Drop the persona — "You are a senior engineer…" adds nothing

Role-play preambles were useful for older, weaker and are now dead weight. Replace the persona with three things that actually help — where to look, what "done" means, and how Claude should check itself.

beginner

Most templates you’ll find online open like this:

You are a world-class senior software engineer with 20 years of experience in enterprise banking systems. You are meticulous, detail-oriented and never make mistakes.

Delete all of it. It does nothing.

Persona preambles were a genuine technique when were weaker and needed to be steered into a register. Current models don’t need telling they’re competent — and the words cost you and attention that could carry real instruction.

What to write instead

Three things do the work the persona was pretending to do:

  1. Where to look. Point at the files, folders, or documents that matter. This is the single biggest quality lever in any prompt.
  2. What “done” looks like. Length, format, scope. Without it you’ll get four pages when you wanted four bullets.
  3. How to check itself. “Then verify each figure against the source and show me the check.”

Bad:

You are an expert financial analyst. Analyse our complaints data and give me your professional assessment.

Good:

Read complaints-q3.csv. Group the complaints by product line and tell me which three moved most versus Q2 in complaints-q2.csv. Under 200 words, one table. Then recompute the totals from the raw rows and show me they match.

The second one is longer, but every extra word is doing something. The first is longer than it looks and none of it is.

The one exception

Telling Claude about your context is not a persona and is genuinely useful:

I’m a business analyst, not a developer — explain anything technical in plain terms.

That’s information it doesn’t have. “You are a brilliant engineer” is information it doesn’t need.

Next tip →

Esc to stop Claude mid-action (the control key)

When Claude is going down the wrong path, press Esc to halt it immediately. This single key prevents most "Claude just deleted everything" horror stories.