Checkpoints
Checkpoints preserve project state while Atom works. If something goes wrong or you want to try a different direction, choose an earlier checkpoint from the conversation.
How Checkpoints Work
Atom saves a copy of the local .prproj before scripted changes that can alter the project. The checkpoint is associated with the matching action in the conversation.
Checkpoints require a saved local Premiere project. Cloud projects and Productions do not support project checkpoints.
Project checkpoints are enabled by default. If saving a large project slows down your workflow, turn them off in Settings > Features > Project checkpoints.
Restoring a Checkpoint
Click a checkpoint bubble to restore the saved Premiere project. Atom reopens the restored project at its original path when Premiere allows it; otherwise it opens a separate branch copy and leaves the original file untouched.
If Confirm reverts is enabled (the default), Atom asks before destructive reverts (going back to an older checkpoint):
- Revert — Restore the selected checkpoint
- Cancel — Stay where you are
- Don't ask again — Disable future confirmation prompts
Turn confirmations off any time in Settings > Features > Confirm reverts.
Editing Messages
When you edit a previous message and re-run it, Atom automatically restores the checkpoint associated with that message before applying the new request. This keeps your project in sync with the conversation.
Branching
Branching creates a new conversation from any previous message. The original conversation stays intact, and the new branch starts from the checkpoint at that point.
What Gets Saved
Each checkpoint is a verified copy of the saved local .prproj, including its bins, sequences, tracks, clips, markers, and project settings. Source media remains in its existing location and is not duplicated.