Identity Forge Vault Save
The Identity Forge vault, explained
- image
You rolled a character you love. Your seed is fixed, so you could reproduce it - but that's the whole problem: it's one specific seed in a graph full of them, and three weeks from now you won't remember which. Identity Forge Vault Save is the pack's answer: a terminal node, used like Save Image, that writes the character to a local vault you can recall anytime with Identity Forge Vault Load. Think of it as favorites, but for people.
How it works
Wire Identity Forge's prompt_json in - that's all the node actually needs. Optionally also wire the rendered image in, and its first frame is stored as a thumbnail for the visual recall gallery. When the workflow runs, the node saves the character and the vault entry shows up in Vault Load's list.
The one decision you make is the name:
name- leave it blank and the node auto-names it: the cosplay/archetype label if one was wired, else a description like "Woman, 25, auburn hair", else "Character N". Auto-names never overwrite an existing save.on_existing- what happens when you type a name that already exists. Default isOverwrite; switch to keep-both (a suffix is added) if you want to preserve older versions. Auto-names ignore this and always keep both.
The saves land under ComfyUI/user/identity_forge/characters/, which is worth knowing for two reasons: it survives pack updates (it's not part of the install), and it isn't cleared when you clean your image output folder - the vault is separate from your outputs.
Using it in a workflow
Because it's a terminal node with no outputs, it sits at the end of the chain like Save Image: Identity Forge → (Vault Save), with the image optionally split off to Vault Save while a copy also goes to your normal preview. Mute the node (Ctrl+M) when you don't want to save - that's the documented way to skip it, and it keeps the node in the graph for when you want it back.
One subtlety that saves confusion: the prompt_json you feed it is the final character, so anything wired through the preset nodes - a Cosplayer, an Archetype, a Modifier - is already baked into the save. What you recall later is the finished thing, not a partial description.
Install and gotchas
Same pack, zero dependencies, fully offline:
cd ComfyUI/custom_nodes
git clone https://github.com/EnragedAntelope/comfyui-identity-forge
Restart ComfyUI, or install via ComfyUI Manager (search "Identity Forge"). Needs ComfyUI 0.25.0+ (V3 API). And the usual pack gotcha: a NoneType error or blank widget on a saved graph after an update means the node is stale - delete and re-add it.
The practical tip that makes this node sing: fix your seed on Identity Forge, generate until you get a keeper, save it with a name you'll actually remember, then set the seed back to randomize. The vault is where the pack stops being a randomizer and starts being a character library.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| prompt_json | STRING | Wire Identity Forge's 'prompt_json' here — the character to save. Any wired Cosplayer/Archetype/Modifier is already baked into it. | |
| name | STRING | Optional name. Leave blank for an automatic one: the cosplay/archetype label if present, else a description like 'Woman, 25, auburn hair', else 'Character N'. Auto-names never overwrite an existing save. | |
| on_existing | COMBO | Overwrite | What to do if you type a name that already exists: 'Overwrite' replaces the saved character, 'Keep both' saves alongside it under a numbered name, 'Skip' leaves the existing one untouched and saves nothing. (Auto names ignore this and always keep both.) |
| imageopt | IMAGE | Optional: the rendered image. Its first frame is stored as a thumbnail for the visual recall gallery. |
Outputs (0)
No outputs