Delete Version In GenAsset
Delete Version In GenAsset — removing with your seatbelt on
- version_id
- status_json
Versioning systems have a dirty little secret: the delete button is more dangerous than the commit button. Delete Version In GenAsset is that button, and the pack is fully aware - that's why this node has a second safety on it. Give it a version_id and it will happily call DELETE on the version, but only if you've also flipped confirm_delete to true. No confirm, no delete.
That two-switch design isn't bureaucracy, it's damage control. A version is someone's approved output, the parent of a branch, or the one reference everyone's agent workflows load. Deleting one by accident in a shared workspace is a "whoops" that takes real effort to undo, so the pack makes the destructive act impossible to do by accident - you have to intend it twice.
How it works
The node does a DELETE request to api/v1/versions/{version_id} with your workspace token. Before it bothers the server, it checks two things: that version_id isn't empty, and that confirm_delete is actually true. Fail either check and you get an error in status_json telling you exactly what's missing - "Set confirm_delete=true to delete a version."
That's the entire mechanism. There's no undo, no trash can mentioned anywhere in the pack's docs, so treat the delete as permanent for the asset's history. Note that this deletes a version, not the whole asset - the asset and its other versions stay put.
Inputs and outputs that matter
Three required inputs: base_url, token, version_id, and the boolean confirm_delete. The version id is the only real work - grab it from a save node's output, List Asset Versions In GenAsset, or the web UI, and double-check it before you commit. confirm_delete defaults to false, which is the entire point: the node ships in "safe" mode and only deletes when you explicitly flip it.
Outputs are minimal: version_id (echoes back what you deleted) and status_json with the server's result. Both are mostly for confirmation.
Installation
Part of the steliosot/ComfyUI-GenAsset pack. ComfyUI Manager → search GenAsset → install, or:
cd ComfyUI/custom_nodes
git clone https://github.com/steliosot/ComfyUI-GenAsset.git
Restart after installing. No extra pip dependencies; just a workspace token (widget, GENASSET_WORKSPACE_TOKEN, or ComfyUI/user/genasset.json).
Common issues
- "Set confirm_delete=true to delete a version." - you forgot the second switch, or you're testing in a workflow that resets the boolean each run. That's the safety working as intended.
- "Paste version_id." - empty input; the node won't guess.
- A version you want is gone - before you deleted, did you check whether it's a branch parent or the promoted current version? The pack doesn't block deleting a promoted version, so if you delete the current one, the asset's
current_version_idpoints at a deleted version until you promote another. Worth checkingPromote Version In GenAssetafter a cleanup session.
The rule of thumb: keep confirm_delete wired to a toggle you consciously flip, not a constant true buried in a saved workflow. Deleting is forever, and the pack's authors clearly believe you should feel the click.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| base_url | STRING | https://genasset.xyz | — |
| token | STRING | ComfyUI/user/genasset.json | — |
| version_id | STRING | Version id to delete. | |
| confirm_delete | BOOLEAN | false | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| version_id | STRING | — |
| status_json | STRING | — |