2 min lesson
Restore the checkpoint before a bad request
Restore the checkpoint before one bad request, rerun the check and inspect the remaining diff.
Check your understanding
Complete the walkthrough "Restore the checkpoint before a bad request".
Outcome: The sorting edit is gone, while the earlier component and hook remain. Inspect the diff before continuing. Checkpoints are local and separate from Git. Use Git to keep permanent history.
Restore the checkpoint before a bad request
Agent run controls
2 steps · ~1 min
Read the failure → Restore from the prompt's ↺
Read this walkthrough as text
Restore the checkpoint before a bad request
Agent run controls
SayThe earlier recent searches work still passes. Restore to the state before the sorting request.
SeeA later request adds recency sorting in searchFilter.ts, and a search test now fails.
DoOpen the checkpoint beside the sorting request, preview the files at that point and restore it.
SeeThe sorting edit is gone, while the earlier component and hook remain. Inspect the diff before continuing. Checkpoints are local and separate from Git. Use Git to keep permanent history.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.
Learn more
Optional practice
Test yourself on Restore the checkpoint before a bad request
QWhat should be true when you finish the Agent run controls practice?