Revisions

A revision captures strategy source and settings at a point in time. Runs refer to their own revision, so changing the current editor does not rewrite an older run's source.

Save your draft

The header marks pending changes as unsaved. Choose Save revision to persist them. Run backtest and Send also save before starting their work.

Draft edits do not have background durable autosave. Save before navigating away or refreshing the browser.

Inspect an older version

Open History and select a revision. The Changes view compares that revision with the working draft. Selecting history does not itself restore the selected source into the editor.

Run selection and revision selection are separate. Before drawing conclusions or publishing, check both the run's revision identifier and the selected publication revision.

Restore a checkpoint

Select the revision you want, then choose Restore selected revision. Restoration creates a new checkpoint from that snapshot; it does not erase intervening history. Preserve any unsaved work you still need before restoring.

After restoration, run again if you need results for the restored working version. An old run remains evidence for its original revision.

Resolve a newer-revision conflict

The Lab rejects saves based on an outdated latest revision rather than silently overwriting newer work. If the assistant saves while your draft has local changes, a banner offers Discard local edits and load latest.

Copy any local changes you want to keep before using that action. Load the latest revision, reapply the intended changes, inspect Changes, and save again. Avoid editing the same experiment in multiple tabs during an active assistant task.

Choose the version to publish

Publication uses the revision selected in History, not unsaved editor contents. Save the final draft, select its revision explicitly, and follow publishing.