GenAsset
GenAsset ComfyUI tutorial

Team handoff checklist

Name assets, add useful metadata, and share stable IDs so teammates can pick up work without guessing.

Goal

TEAMCloud Run validated

Make a saved asset easy for another person to understand and reuse.

Setup

  • Use stable asset names instead of one-off test names for team work.
  • Put creative notes, ownership, approval status, and source prompts in metadata.
  • Share asset_id and the exact version_id when a teammate must start from one version.

Steps

  1. Open the asset in GenAsset or load it in ComfyUI.
  2. Add a short handoff note such as approved direction, needs brighter foreground, or branch for color pass.
  3. Copy asset_id plus version_id into your issue, chat, or production tracker.
  4. Ask the teammate to load exact version first, then fork or branch.

Validated run

  • The tutorial asset was renamed, patched, branched, and promoted while preserving traceability.
  • The tested workspace belonged to stelios.sotiriadis@warestack.com; no token value was shared.

Next

Fork a teammate asset

Create a separate asset when your direction should not modify the source history.