Checkpoint flag on an AI chat message
Checkpoint

Appifio Creator · Lesson T10 · Technical

Checkpoint vs History
vs Versions (+ Undo)

Four layers of “go back” - different scopes. Mix them up and you lose work, or think you’re backed up when you aren’t.

Goal: Pick the right tool for the situation; know Checkpoint flags only on the newest AI message; tell History’s “Current” apart from the preview Current button.

Time: ~12 min · Before: E01, E02, H04 · After: T11

UI: Undo · Redo · History · Edit history · Restore this point · Delete · Current (in History) · checkpoint flag · Save checkpoint (manual) · Versions · Create new (Clone)/(Clean) · Refresh

1. Decision diagram

Undo 1-few Inspector clicks? → Undo / Redo
Jump to a recorded editor action? → Edit history → Restore this point
Roll back files + chat to an AI milestone? → Checkpoint (flag on AI messages)
Parallel experiments / split sessions? → Versions tab · Clone or Clean · (optional) Sync from site / Compare 2 versions
Site online + “N rev behind” → Diff/Sync before Save - avoid overwriting live with an old session
Gray flag only on the newest AI message - “Only the latest AI message can save a checkpoint…”

2. Comparison table

AspectUndo/RedoHistoryCheckpointVersions
ScopeRecent stepsEditor action pointsFiles + chat to an AI markWhole session
UI labelUndo / RedoEdit historyFlag on AI messageVersions tab
How createdAuto per editAuto pointsGray flag / manualClean / Clone
RiskWon’t undo past live SaveDoesn’t cover every AI writeLoses work after the markClean = empty; Clone uses a slot

3. Practice steps

Edit History popover in Inspector toolbar
Edit History
  1. Undo: Toolbar Undo / Redo after a bad Inspector/drag (C03).
  2. History: History button → Edit history panel → pick a point → Restore this point (or Delete). Empty = History is still empty. Panel label Current = where the undo cursor sits - not the preview Current button.
  3. Checkpoint: After a good AI reply → gray flag → Checkpoint saved successfully. Restore: green flag → Restoring checkpoint.... Newest AI message only.
  4. Versions: Versions tab → Create new (Clone) before a big experiment; read rev / Unsaved / behind badges; when Site online → Sync or Diff before Save; use Compare 2 versions when needed; Clean only when you mean to start over → Refresh.

4. Comparisons · Limits · Security

Versions Clean and Clone cards
Versions
  • Git: Checkpoint ≈ light commit; Versions ≈ branch; History/Undo ≈ local undo - not a Git/CI substitute.
  • Figma version history: closer to Versions than chat-tied Checkpoint.

Restoring a Checkpoint can drop work after that mark. Don’t casually clone sessions that hold secrets. Safe pipeline: Clone (K02) → edit → Diff → Checkpoint when stable → Save changes.

5. Issues · Checklist

IssueFix
Can’t checkpoint an older messageBy design - newest AI message only
History empty after a big AI writeUse Checkpoint/Clone - History doesn’t cover every AI write
Confusing History “Current” with previewCheck panel context (H04)
Clean wiped the site by mistakeAlways Clone; Clean only on purpose
  1. Do you pick Undo vs History vs Checkpoint vs Versions correctly?
  2. Before a large prompt, did you Clone?
  3. Do you know Checkpoint only works on the newest AI message?

Next: T11 - AI tokens & Prompt profile

Appifio Creator · User guide · T10