Use versions, forks, undo, and editor copies

Keep two approved versions of one lesson

Customer success needs a shorter kickoff cut while support must keep its existing tutorial. Open the approved project and fork or copy the appropriate version before changing its ending. Check the title and destination of each cut.

If one factual correction should reach every viewer of an uploaded hosted lesson, make the replacement live in the library. A separate fork would give you another project to distribute. Replace an uploaded lesson at the same link.

Preserve each approved audience cut (illustrated guide)

A rendered output and a saved conversation checkpoint are different. Preview or download an earlier render without changing the project. Use Saved versions to restore a checkpoint or fork it when you want another direction.

Before changing saved work

Open the project from Projects and confirm that you own the conversation you intend to change. Wait for active work to finish. Keep its URL and use a separate name for any fork so you can find both directions later.

Preview an earlier render

1. Open the conversation containing the video.
2. Open Versions when more than one rendered output is available.
3. Select an output and play it.
4. Choose Download on a paid plan if you want a file of that output. Selecting it does not restore the editable project.

To continue from an earlier checkpoint, open Saved versions in a conversation you own. Restore a checkpoint to make it the active project state, or fork one to keep a separate path. Eligible message actions also offer undo or redo. Confirm the active version before requesting another generation, which can use credits.

Restore or fork a saved version

1. Open your conversation from Projects and wait for any active work to finish.
2. Open Saved versions and choose the checkpoint you want.
3. Choose Restore to continue from that checkpoint, or Fork to create a separate direction.
4. Check the active conversation and replay the result before sending another revision.

Undo or redo a conversation turn

Eligible messages offer undo or redo actions. Read the action and confirm the intended checkpoint before continuing. Use Fork from Saved versions when you want a separate direction, and check which conversation is active before requesting another generation.

Continue older or separately saved work

Open the intended project from Projects before making a change. If you imported or separately saved an older project, check its name and preview; do not assume edits to another conversation automatically appear in it.

If an earlier result is missing

Confirm you opened the original conversation and that it has more than one generated output. Keep the conversation link when contacting Support so they can identify the work.

Contact Support when work is missing

Stop undoing, forking, or regenerating when an expected render or checkpoint is missing. Keep every related project and send Support the original project URL, approximate time, last visible version or error, and names of any separately saved projects. Recovery is not guaranteed.