Press Escape to Interrupt Claude Mid-Response and Change Direction
You asked Claude to refactor a function and it starts rewriting the entire file. Or it's generating a long explanation when you just wanted the code. Don't wait for it to finish — press Escape to stop it right where it is.
> refactor the getUserById method to use early returns
Claude starts editing... changing the method... now it's moving to a
different file you didn't ask about...
[Press Escape]
> stop — only change getUserById, leave everything else alone
When you press Escape, Claude stops generating immediately. Any tool calls that already completed (file edits, commands) stay in place — they're not rolled back. But anything Claude was about to do next gets cancelled.
This is different from Ctrl+C, which kills the entire process. Escape is a soft interrupt — it stops the current response but keeps your session alive with full context. You can immediately type a new prompt to redirect.
A few situations where Escape saves time:
- Wrong direction — Claude misunderstood your intent and is editing the wrong files
- Too verbose — you wanted a quick answer but Claude is writing an essay
- Runaway changes — Claude is making more changes than you asked for
- Slow response — you realize you need to rephrase your prompt before Claude finishes
It's also useful as a feedback mechanism. Interrupt, tell Claude what went wrong, and it adjusts. This is faster than waiting for a full wrong response and then correcting after the fact.
If Claude was mid-edit when you interrupted, the file may be in a partial state. Just tell Claude to finish what it started or revert the change — it knows where it left off.
Escape is your steering wheel — use it early when you see Claude heading somewhere you don't want to go.
via Claude Code
Log in to leave a comment.
When typing feels slow — describing a complex bug, explaining architecture, or thinking through a problem out loud — press Option+V to switch to voice input. Speak naturally and Claude Code transcribes your words into a prompt, so you can describe what you need at the speed of thought.
Closed a session and realized you weren't done? Pass --continue (or -c) when launching Claude Code to pick up exactly where you left off — same context, same files, same conversation history — without re-explaining what you were working on.
The -p (print) flag runs Claude Code as a one-shot command — ask a question, get an answer, and return to your shell. Perfect for quick lookups, scripting, piping output, and integrating Claude into shell workflows without starting a full interactive session.