# Every version of a take

> In short: The History tab lists every version of the take on the stage: what it was made from, who made it, when, and what it cost. Versions are numbered v1, v2, v3 in the order they were made, and a number never changes.

Applies to: v0.8 · Last reviewed: 2026-11-02 · Canonical: https://docs.zymcos.com/product/version-history/

The right column has a **History** tab. Put a take on the stage — click it in the Viewport's
strip or in Files — and History lists every version of it: what it was made from, who made
each one, when, and what it cost.

## What a version is

Every generated image belongs to a **family**: the first version, and everything later made
from it — a retake, an edit, a variation, a reframe. Each has a number, **v1, v2, v3…**, in
the order they were made, and the number never changes. A version made from v2 after v3
already exists is v4: a branch, two lines of work from one image.

A file you brought in (a reference, an upload) is not a version of anything. History says so
rather than showing a family of one that is not one.

## Reading the list

One row per version:

- a thumbnail, its number and its name — the one you gave it, or the derived one;
- **who made it**: a person, **CODA** when CODA wrote the recipe and a person sent it, or a
  run;
- **when**, and **what it cost**. A cost marked *est.* is what was reserved rather than what
  was charged; a version with no reliable figure shows none — a blank is never a zero;
- **★** where the take is circled, and **Final** where a person accepted it as the shot's final.
  The Files tab can show either.

A **withdrawn** or **erased** version stays in the list and is marked, so the versions after
it still show where they came from. The row of the version on the stage has the brand-coloured outline, the same one any other thing you are looking at has.

**Click a row** and that version goes on the stage. A withdrawn or erased version has no
stage to go to, so its row is not a button.

## The path to each final

At the top of History, above the list, **Path to final** sums up the production: every take
that was accepted as a shot's **final**, and what it took to get there. Until the first take is
accepted as a final, it shows your **★ circled** takes instead, and says so.

For each final (or circled take), one row:

- its number and its name;
- **how many versions came before it** — every version its family held before this one,
  including a branch that was tried and left behind, because it was made on the way here.
  A ★ on the first version says *first try*;
- **what those versions and this one cost**, added up from what the providers actually
  charged. Where the ledger has no figure for a take — a model with no rate, or a run not
  settled yet — the row says so beside the sum, *$0.12 + 1 unpriced*, and a path with no
  settled figure at all says *1 unpriced* rather than a zero;
- the operation that produced it — *remix*, *variation*, *generated* for a first version —
  and the model.

Under the rows, the operations and models that produced your finals are counted, most
first, so *remix ×3 · variation ×1* is a fact about this production and not an impression.

The same figures, in four lines, sit on the **Home** tab for the production on screen:
how many finals in how many families (with how many ★ circled beside them), versions-to-final
and cost-to-final **on average**, and what produced the finals most often. Averages, not totals: two circled takes in one
family share the versions before the first, and a total would count them twice. A path the
ledger could not fully price is counted beside the average, never averaged in as nothing.

With no ★ yet, both say so — and how many families are waiting for one.

## Family and Shot

**Family** (the default) is the take's own versions. **Shot** widens to every family on the
shot the take belongs to, each headed by its first version's name, so two lines of work on
one shot read as two. A take that is not on any shot has no shot to widen to; the Shot
button says so and stays put.

## Comparing two versions

Press the **compare** icon on two rows and a panel shows what differs between their
recipes — only what differs:

- the **prompt**, with the removed words struck through and the added ones highlighted, so a
  changed adjective reads as one change and not as two paragraphs;
- the **parameters** whose values moved, before → after;
- the **model**, when it changed;
- the number of references, when the list changed;
- one line naming what stayed the same.

Two identical recipes say so. The comparison is in the page address, so it can be linked and
Back leaves it. Press either icon again to close it.

## Branch from here

The **branch** icon on a row takes that version's recipe and puts it into CODA's open
conversation as a proposal card, with the version as its parent. Nothing is generated and
nothing is spent by the click: the card in CODA is where you send it, edit it first, or leave
it. CODA switches to that conversation and scrolls to the card; History still says that
nothing has been spent, because the card looks like every other proposal.

One thing the card does not carry, said plainly: the original's random **seed** (a branch is
a new take). It carries every shot the take was made for, and says so — "Will be a take of
shots 2, 3." — so a branch of a take made across two shots is made across two shots. If those
shots commit different versions of the same character in the bible, no card is made: CODA says
which character and which versions, and the way forward is one take per shot, or locking the bible
so the shots agree.

## Variations and Animate

Two more ways to make a version start from the stage. Under a take, set apart from the other
controls by a warm rule — at the end of the first row on a wide stage — the **Iterate** group
offers **Variations** and **Animate** for a generated still:

- **Variations** proposes the take's own recipe again — the prompt and the settings — with the
  random seed dropped, so the result is the same idea, drawn differently.
- **Animate** proposes a clip that starts on this still, with the still's own prompt as the
  motion prompt. To animate it with different words, use *Use as reference* instead, which
  asks for them.

Neither generates by itself. Each puts a card in CODA's open conversation — with the version
it builds on named on the card, and its quote — and CODA switches to it. **The card's button
is the one click that spends.** Where the catalogue has no rate for the model, the card says
so plainly (*Unpriced — the ledger cannot quote this before it runs*; in a narrower CODA just
*Unpriced*, with the sentence on hover) and the button reads *Generate — unpriced* (in the
narrowest, *Generate* with a *$?* marker): the run is recorded as unpriced, never as free.
Once the card is sent, its foot is one line — how the job is doing and what it cost — and at
most one button: *Show on the stage* when a still or a clip has landed.

The new version records the edge — *variation of v2*, *animate of v2* — in History like any
other. A clip, a file you brought in, or a withdrawn take offers neither control, and the
button says why. Upscale, reframe and extend are not offered yet: each arrives once its
model is verified.

## The graph, drawn

A rail beside the rows draws the lines from each version to its parent: a retake continues
its parent's line, a branch leaves it on a line of its own. The same edge is written on the
row — "remix of v2" — so nothing is only in the picture. A parent cut by the version cap is a
dashed stub from above, never a line to a guessed row.

Each row also carries the take's 👍/👎 counts, exactly as Files shows them, and names its
shot where the name does not already say it: a take you titled shows "Shot 4" under its
title, or "Shot 4 · Shot 5" if it was made across several. An untitled take already says its
shots in its name ("Shot 4 · take 2", "Shots 4–5 · take 1").

## A region edit's mask

A version made by **Edit region**, **Remove object** or **Mark up** on the stage (see
*Editing a region on the stage* in [Your files](https://docs.zymcos.com/product/your-files/)) was made from two things:
the version it came from, and the region you painted. The painting is kept as a file of its
own in `refs` — "Edit region mask", "Remove object mask" or "Mark-up" — and History keeps it
among the version's inputs, beside the parent, so what was asked for is never only in the
prompt. The rows say the parent ("regional edit of v2"); the mask is in Files.
