Use versions, forks, undo, and editor copies

Know what each action does

• Fork from here can appear on eligible completed checkpoints in newer conversations. It starts a new conversation branch and leaves the original intact.
• Undo to this point can appear on an eligible earlier checkpoint. It rewinds the current branch and discards its later turns; it is not offered on the latest completed point.
• Versions shows a read-only gallery for newer conversations created with version tracking; it is not available on every older project.
• Open in editor creates an independent full-editor copy. Later conversation edits and editor-copy edits do not synchronize.

Choose safely

1. Fork before a major change when you may want both creative directions.
2. Use undo only when you intend to remove the later turns from the current branch.
3. Use Versions to inspect a tracked render, then use the available fork or undo action when you need a working branch.
4. Open in editor only when you need timeline-level manual control and are ready to maintain a separate copy.
5. Rename the resulting projects so the conversation, fork, and editor copy are easy to distinguish in Projects.

Whole-script rewrites

When a storyboard or video already exists, a whole-script rewrite can affect most of the project. Preserve the current work in a fork when Studio offers that path, then make the broad rewrite in the new conversation. Use a normal targeted revision when only a few lines or scenes need to change.

If the version you expect is missing

Check the original conversation, its forks, and any project marked as an editor copy. Older conversations may not have the Versions gallery. If undo removed work you still need and no fork or saved copy exists, contact Support with the project URL and approximate time; recovery is not guaranteed.