GenAsset
GenAsset ComfyUI tutorial

Fork a teammate asset

Create a separate asset copy from an existing GenAsset version before exploring a different creative direction.

Goal

TEAMCloud Run validated

Create a separate asset copy before exploring a different direction.

Setup

  • Fork when the new direction should have its own asset history.
  • Branch when the new direction belongs under the same asset.
  • Use exact version IDs for forks so the source is unambiguous.

Steps

  1. Load the source asset/version.
  2. Use the fork workflow or Fork Asset node with a new asset name.
  3. Queue once and copy the new asset_id.
  4. Rename the fork if needed so it is readable in Recent Assets.

Validated run

  • Cloud Run prompt b92ca98f-9006-48a3-a8aa-25e7a07edb4e forked the jungle mech asset.
  • Created asset 7add9faf-adcc-4145-b3f8-d09054182c93 and version eefcbee0-74fe-49f0-af82-e79b2fcd4404.
  • Cloud Run prompt 616bf2c5-b6ae-4525-ad3a-2a5801adcbed renamed the fork successfully.

Next

Create a branch

Keep alternatives inside one asset history when that is the better team model.