Workflow snapshots & version history

Snapshots are immutable, point-in-time captures of the entire workflow graph — nodes, edges, prompts, scripts, tools, and positions.

Key concepts

• Automatic creation: after every graph-mutating node edit (clay workflows nodes create|update|delete; Sculptor: edit_node) and when a run starts. data[0] is newest-by-createdAt, not necessarily the current graph. Sharing/binding a trigger onto an existing node does not snapshot — undo that create by deleting the trigger, not restore. Settings-only trigger update/delete also do not snapshot — revert or recreate the settings; do not delete the trigger and do not restore. graph format takes two snapshots when validation has no errors (pre-layout, then post-layout); details under Undo.
• Restore does not reshuffle the list: snapshots restore rewrites the draft but does not create or reorder snapshots. Duplicate hashes reuse the existing row without updating createdAt. After a restore, data[0] can be a later history entry that is not the current graph, so the next edit's data[1] is often that stale entry rather than the pre-edit graph. Compare the latest snapshot to the current graph (or find the list row that matches) before treating data[1] as the undo target.
• Content-addressed: Each snapshot has a SHA-256 hash of its contents. Identical workflow states deduplicate to the same hash
• Immutable: Once created, a snapshot's graph content never changes
• Run isolation: Runs are pegged to a specific snapshot. Editing the workflow doesn't affect in-flight runs