Skip to content

Checkpoints & rollback

Building with an agent means experimenting, and experimenting means sometimes going down a path you want to undo. Checkpoints make that safe.

What a checkpoint is

A checkpoint is a snapshot of your entire project at a moment in time — backed by a real git commit. Factorly creates one automatically at the end of every agent turn, so your history is a clean, honest timeline of working states.

Because checkpoints are real commits, they're part of the same git history you get when you export to GitHub. Nothing about them is proprietary.

Rolling back

Changed your mind? Preferred the version from five steps ago? Open the project history and restore any earlier checkpoint with a single click. Your project files snap back to exactly how they were at that point, and you can pick up building from there.

This is the safety net that makes it worth being bold:

  • Try a risky refactor — if you don't like it, roll back.
  • Ask for a redesign — keep it, or return to the previous look.
  • Explore two directions — checkpoint, branch off in your head, restore.

A typical flow

  1. You ask for a feature. The agent builds it → checkpoint A.
  2. You ask for a redesign. The agent reworks the UI → checkpoint B.
  3. You decide you preferred the original layout.
  4. Restore checkpoint A. Done — you're back, no work lost.

Next: bring your own context with Attachments.