Skip to lesson
Exit
Checkpoints, Queueing and Mid-Run Control1 / 2

2 min lesson

Restore from the bad prompt's ↺ without losing the good work

Explain the practical point behind "The restore landed just before the bad prompt, with the earlier work still in the diff."

Step 1 of 2

The job: you can intervene during a run and recover from a bad direction. Start with this check: The restore landed just before the bad prompt, with the earlier work still in the diff. Keep it small enough to check the result yourself instead of taking the summary on trust.

Restore from the bad prompt's ↺

0:31 · narrated
Read this demo as text
  1. A second prompt sent the agent into the file searchFilter.ts, and a search test now fails. You don't debug forward through a wrong turn. You restore to just before it.
  2. Click the restore arrow on the bad prompt. Not the first one. The component and hook survive; only the filter edit is gone. And the bad prompt returns to the composer for a rethink.
Primary path: restore from the bad prompt's ↺ without losing the good work.

Practice next: Now run the walkthrough: restore from the bad prompt's checkpoint and keep the good diff intact.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.