How to stop or redirect Claude Code mid-task without losing its work

TL;DR Two keys, two intentions. Esc stops the running tool cold: you keep the work done so far and redirect with a fresh prompt, but you lose whatever action was in flight. Typing a correction and pressing Enter interrupts nothing: the current tool finishes and Claude picks up your note on its next step. Hit Esc when it's on the wrong track; type and Enter when you just want to nudge the direction.

Claude Code works in a loop: it gathers context, acts with tools, and verifies, chaining decisions together until the task is done. You're part of that loop, and you can step in without restarting the session or losing context. There are two ways to do it, and the difference between them comes down to one thing: what happens to the action running right now.

Result:

> Refactor the payments module           (Claude is editing files…)

⏺ Edit  src/payments/checkout.ts
  ↳ Running…               [you press Esc]

⎿  Interrupted · Claude keeps what it did and waits for you

The brake and the steering wheel

1. Esc — the emergency brake

Press Esc once to stop the response or tool call mid-turn. Claude cancels the in-flight action, keeps everything it had already done, and waits for your next instruction. From there you redirect with a fresh prompt.

Reach for it when Claude is clearly on the wrong track: editing the wrong file, building a solution you don't want, or spinning out a long explanation you never asked for. You cut it off, keep the earlier work, and point it somewhere else.

2. Type and Enter — the steering wheel

If instead of Esc you type a correction and press Enter, nothing gets interrupted. The running tool finishes its work and your message lands at the next decision point: Claude reads it and adjusts its next step before moving on.

Use it when things are going fine but you want to course-correct on the fly — "use zod instead of yup", "don't touch the tests yet" — without throwing away the action already running.

3. The decision: is the current action worth keeping?

That's the whole rule:

• If the in-flight action is not worth keeping (it's about to break something, it's headed the wrong way) → Esc. Stop cold and redirect.
• If the in-flight action is worth keeping and you only want to shape what comes next → type and Enter. Let it finish, then hand it the new direction.

Two things so nothing catches you out

Typing and Enter queues, it doesn't abort. Don't expect your message to halt the current tool: it applies on the next step, not this one. When you need an immediate cut, that's Esc.

Esc doesn't always cut instantly. Deep in a long chain of tool calls, or when you're driving Claude over Remote Control, it can lag or miss the first press — keep at it. And mind the double tap: with text in the prompt, Esc Esc clears your draft; with an empty prompt, Esc Esc opens the rewind menu to undo changes, which is a different job.

Just want to ask something without touching the task? That's what /btw is for: it answers in an overlay and Claude keeps working, none the wiser.

Reference

Official docs: How Claude Code works — Interrupt and steer