Checkpoints and Finals

Use checkpoints to keep creative history visible, and mark finals when a result is worth saving or sharing.

Checkpoints

A checkpoint is one completed creative step. It records the prompt, plan, target, generated assets, failures, and cost records.

• Compare direction: move between checkpoints to see how the idea changed.
• Recover running jobs: server image jobs can reconnect to a saved checkpoint after reload.
• Track failures: failed directions stay visible without polluting saved assets.
• Keep context: the next Auto Mode run can include the current checkpoint summary and included reference packs.

Example checkpoint trail:

1. Checkpoint 1: initial iced coffee directions, 3 images.
2. Checkpoint 2: more like Version A, calmer, used Brand.
3. Checkpoint 3: animate final hero image, 1 video.

Generation activity

The activity tray appears near the composer when a checkpoint is queued, running, taking longer than expected, failed, cancelled, or ready to reconnect.

• Cancel: stop an active server image job when cancellation is available.
• Reconnect: resume polling an existing server job after reload or temporary polling loss.
• Retry: prepare the composer from a failed or stuck checkpoint without auto-spending again.
• Cost context: see the related estimate next to the job state when a cost record exists.

Retry fills the composer and focuses it. Press Generate again only after the prompt still looks right.

When a checkpoint used included reference packs, the prompt panel can show a compact label such as "Used Brand + Product". That label is stored on that checkpoint, not across every session or project.

Finals

Finals are assets worth keeping for review, sharing, or future reference.

1. Review generated versions.
2. Mark useful work as final.
3. Use finals later for sharing, references, or the short list.

In VideoBrainstorm, a final can become new context. Save what is useful, then generate from it when the idea needs another pass.