Skip to main content
Use checkpoints when a run reaches a useful intermediate state before trying something risky.

Create a checkpoint

Branch from a checkpoint

When to branch

  • the first attempt found a useful direction but overreached
  • a risky patch needs a smaller alternative
  • reviewer feedback changes the goal
  • a benchmark direction needs a second controlled attempt

Expected evidence

  • parent run ID
  • checkpoint ID
  • child run ID
  • message explaining the changed direction
  • final report comparing the branch to the parent