Load Current Version For Asset

Here's a subtle thing about GenAsset that this node exists to exploit: "latest version" and "current version" are not the same thing. You can keep generating experiments - each one becomes the latest - but the current version is whatever you've promoted as the official one. Load Current Version For Asset is the node that always fetches the official one.

That distinction matters the moment you use GenAsset like a real team. When you load "the asset" for an edit, you almost never want the most recent draft; you want the approved state. This node gives you a one-input shorthand for "the asset's current version, please," so you don't have to track version ids yourself.

How it works

You give it an asset_id (UUID). It fetches the asset record from api/v1/assets/{asset_id}, looks at the asset's current_version_id (the one set by Promote Version In GenAsset), and loads that specific version's payload - image, workflow_json, and metadata_json. If the asset has no promoted current version, it falls back to the highest version_number. Either way you get the preview image and the stored recipe, and the status_json tells you which version it chose.

So the workflow you can build is: generate experiments → promote the good one to current → hand a Load Current Version For Asset node to a teammate or an agent, and they always see the approved state no matter how many drafts landed since. That's the "current" semantic working for you.

Inputs and outputs that matter

Three required inputs - base_url, token, asset_id - and asset_id is the only one you'll change. The tooltip calls it out as required, so this node doesn't do the "empty means latest workspace asset" trick; it wants a real asset UUID. Get it from a save node's output, from Find Assets In GenAsset, or from the web UI.

Outputs are the standard load set: image, asset_id, version_id, workflow_json, metadata_json, and status_json. Same recipe format as the other load nodes, so workflow_json feeds straight into Load Recipe To Widgets if you want editable values back out.

Installation

It's in the steliosot/ComfyUI-GenAsset pack, installed like the rest of them. ComfyUI Manager → search GenAsset → install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/steliosot/ComfyUI-GenAsset.git

Restart, and make sure you have a workspace token - either pasted in the token widget, set as GENASSET_WORKSPACE_TOKEN, or in ComfyUI/user/genasset.json. No extra dependencies to worry about.

Common issues

• "No versions found for this asset." - the asset exists but has no versions yet (or the token can't see them). Save something to it first.
• It loaded a version you didn't promote - when there's no explicit current version, the node takes the highest version number. If you expected something else, promote the right one first, then load.
• The current_version_id semantics confuse you - you're not alone. The promotion happens via Promote Version In GenAsset, and until you run it, "current" just means "newest number." The node is honest about what it loads; make sure your process is too.

This is one of those quiet nodes that earns its keep in automation. It's not flashy, but it's how you make "the asset" a stable, meaningful thing other people can build on without a conversation first.