Course-correcting mid-task

Claude is working. You’re watching. And something’s off — it’s editing the wrong file, or taking an approach you know won’t work, or sounding weirdly confident about a thing you’re certain is false. Your finger hovers over the Esc key.

Press it.

Esc stops Claude mid-task and hands you back the prompt. Whatever it was doing pauses, and you get to redirect. It is not rude, it is not wasteful, and it is almost always the right call the moment you sense drift.

The three flavors of “off”

Drift comes in three shapes, and it’s worth being able to name them:

Wrong direction. Claude is solving a slightly different problem than the one you asked. You wanted a fix; it’s doing a redesign.
Right direction, wrong choice. It’s in the correct file, working on the correct thing — but using a library, pattern, or approach you don’t want.
Spinning. It tries something, it fails, it tries almost the same thing again. Twice is a coincidence. Three times is a signal.

Any of these is a reason to reach for Esc. You don’t have to be sure it’s going wrong — a strong hunch is enough. Pausing costs you nothing; you can always tell it to continue.

The math of interrupting early

Here’s why “early” is the whole game. Every minute Claude spends working in the wrong direction is a minute of work you will either have to revert or quietly live with. So:

Interrupt at minute one, and you lose a sentence — you redirect and you’re back on track.
Interrupt at minute ten, and you lose ten minutes of work, plus the time to untangle it.

The cost of waiting isn’t flat. It grows with every file Claude touches. The brakes get more expensive the longer you don’t press them.

The thing that trips people up

Politeness. People let Claude finish out of a faint sense that interrupting is rude — like talking over someone mid-sentence. Let that go. Claude doesn’t have feelings to bruise and isn’t offended by Esc. Watching it carefully build the wrong thing to be polite is the most expensive courtesy in software.

How to redirect after you stop

Once you’ve hit Esc, keep the correction short and specific:

“Stop — use react-hook-form instead of Formik.”
“You’re editing the wrong file. It’s Header.tsx, not header.tsx.”
“That’s not the bug. The problem is in the API call, not the component.”

Claude picks up from your redirect. The work it already did stays (you can keep or undo it), and the new direction starts from where you are now.

What’s next

Course-correcting works when a nudge can fix things. But sometimes a conversation goes bad in a way that no nudge can rescue — and pushing harder only makes it worse. The next lesson is how to recognize that moment and the surprising move it calls for.