2 min lesson
Roll back a bad prompt without losing the good work
Complete "Roll back a bad prompt without losing the good work". Check the final state against the lesson before you move on.
Check your understanding
Complete this walkthrough: Checkpoints — roll back a bad prompt without losing the good work.
Outcome: Finish with the result shown in the final walkthrough step.
Checkpoints — roll back a bad prompt without losing the good work
Agent run controls
2 steps · ~1 min
Read the failure → Restore from the prompt's ↺
Read this walkthrough as text
Checkpoints — roll back a bad prompt without losing the good work
Agent run controls
SayYou don't debug forward through a wrong turn — you roll back to before it.
SeeA second prompt — 'Also rank results by recency' — sent Agent into searchFilter.ts, and a search test now fails.
DoEvery prompt carries its own ↺ restore. Click the one on the BAD prompt — not the first one, which would throw away the good work too.
SeeThe component and the hook survive; only the filter edit is gone. The bad prompt lands back in the composer for a rethink, and the Changes panel still shows the good diff intact. Checkpoints are local and separate from Git, so anything you need permanently still has to be committed.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.
Learn more
Optional practice
Practice: Roll back a bad prompt without losing the good work
QYou've applied it. What actually proves the work is done, not just a plausible answer?