You do not have to sit and watch Claude finish something you already know is wrong. The instant it heads in the wrong direction, press Esc. It stops immediately.
This is one of the most underused habits in Claude Code. People wait politely for a long, wrong response to complete, then explain what they actually wanted. Interrupting early is faster and cheaper. You catch the mistake at the moment you spot it, while the context is still fresh.
When to reach for Esc:
- Wrong file or wrong approach. You see Claude editing the wrong module, or reaching for a library you do not use. Stop and point it right.
- Scope creep. It starts refactoring things you never asked about. Stop and narrow the task.
- Misread request. It clearly misunderstood what you meant. Stop and rephrase before it builds on the misunderstanding.
The flow is simple. Press Esc, then type your correction:
[Esc]
Stop — don't touch the API routes. Only change the middleware.
Because you stopped it early, the conversation so far is still useful. You are refining the same task, not starting over. Claude keeps what it learned and applies your redirection.
Esc is also your general stop button. If a command is running longer than you expected, or Claude is off exploring files you do not care about, Esc brings it back to you.
Think of it like pair programming out loud. If your partner started coding the wrong thing, you would speak up right away, not let them finish the whole function first. Esc is you speaking up. Use it freely; interrupting is not rude here, it is how you keep the work on track.
Comments
Be the first to comment.