Cuando Claude se equivoca
O escúchala
Cuando Claude se equivoca
2:27 · versión en audio de esta lección
Claude will get things wrong. Not occasionally — regularly. It will misunderstand you, edit the wrong file, or confidently do something that is almost right.
This is the most useful lesson in the module, because the difference between people who get value out of Claude Code and people who give up is not prompting skill. It is knowing what to do in the next thirty seconds when the output is wrong.
Stop it mid-task
If Claude starts doing something you did not ask for, do not wait for it to finish.
Press Esc. It stops immediately.
You can then type what you actually meant. You do not need to start the whole session over, and you do not need to apologise to it.
Undo what it changed
Claude Code keeps a snapshot of your files before every message you send. To go back, make sure the input box is empty, then press Esc twice.
Does the same thing as pressing Esc twice, if you prefer typing it.
/rewindA menu appears listing every message you sent this session. Pick the point you want to return to, then choose:
| Option | What it does |
|---|---|
| Restore code and conversation | Undo the file changes and forget the discussion |
| Restore conversation | Forget the discussion, keep the files as they are |
| Restore code | Undo the file changes, keep the discussion |
| Never mind | Back out, change nothing |
Most of the time you want Restore code and conversation: it puts you back exactly where you were before the thing went wrong.
What rewind does not cover. It only tracks files Claude edited directly. If Claude ran a command that deleted, moved or copied a file, rewind cannot bring it back. It is a session-level undo, not a backup. Anthropic's own docs put it plainly: think of checkpoints as "local undo" and Git as "permanent history". You will learn Git in Module 5.
Say what is wrong, specifically
Siguiente
Lo que Claude tiene permitido hacer