Use versions, forks, undo, and editor copies

Use this when

Use this guide when you want to preserve two creative directions, inspect or download an earlier render, undo later conversation turns, or understand why an editor copy does not match its source conversation. It also explains what is—and is not—recoverable after an unwanted edit.

Versions is a view-and-download gallery, not a restore or revert control. Opening or downloading an earlier render does not make it the active editable version.

Before you start

Open the exact conversation from Projects and identify whether you are in the original, a fork, or a full-editor copy. Rename similar projects before making another major change. Use a fork before experimenting when Fork from here is available; do not use Undo until you accept that later turns on the current branch will be removed.

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 appears in the conversation top bar when that conversation has at least two rendered versions. It shows each render newest first with a thumbnail, duration, and timestamp; you can preview or download one without changing the current session.
• Open in editor creates an independent full-editor copy. Later conversation edits and editor-copy edits do not synchronize.

Preview or download an older render without changing current work

Open Versions in the conversation top bar, select the earlier render by its thumbnail and timestamp, and preview or download it. That action does not disturb the current session and does not restore the older render as the editable version.

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 preview or download an earlier render. Do not expect that action to create an editable branch or change the current version.
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. Asking the agent for a broad rewrite now runs in place in the same conversation, with a confirmation dialog first, so you don't lose the surrounding context by forking. Changing the narration or voice cast on an existing storyboard still starts a fork so you can compare directions. Use a normal targeted revision when only a few lines or scenes need to change.

If the version you expect is missing

Confirm the conversation has at least two completed renders, then check the original conversation, its forks, and any separately named editor copy. Reopen the exact conversation once from Projects. If Versions is still missing, an expected render is absent, or Undo removed work and no fork or saved copy exists, stop and contact Support; recovery is not guaranteed.

Expected result

A fork remains editable without altering the original branch; Undo rewinds only the current branch; Versions opens an earlier render for preview or download without disturbing current work; and Open in editor creates a separately saved project that no longer synchronizes with the conversation.

Contact Support when work is missing

Do not keep undoing, forking, or regenerating when a render or set of turns is missing. Send Support the original project URL, approximate time of the missing work, last visible version or error, browser, the names of any forks or editor copies, whether you reopened the conversation once, and whether Usage shows a credit change. Keep every related project until the review is complete.