EditUtils: Load Condition lrzjason

If you've ever waited through a Qwen-Image-Edit encode just to change one word in your prompt, LoadCondition_EditUtils is the node that makes that wait go away. It's the read half of the pack's condition-cache pair (the write half is SaveCondition_EditUtils): it loads a CONDITIONING tensor straight from ComfyUI/models/conditions/ and hands it to your sampler - no CLIP, no VAE, no vision-encoder pass. Same reference image, same system prompt, infinite prompt tweaks, one encode total.

The input is a single filename dropdown that lists every .ckpt in the conditions directory, so no typing, no guessing paths. The output is one CONDITIONING socket, which is the thing the whole pack is built around: the conditioning carries the reference latents inside it, so when you load a saved condition you get the reference-aware state back in one step. Wire it straight into your KSampler's positive input and you're done.

The workflow this exists for: you save a condition once at the end of a "good enough" encode, then treat that .ckpt as a frozen snapshot. Every subsequent run skips the expensive parts. It's the same idea as caching a CLIP text encode, except here the cache is durable across ComfyUI restarts and across workflows - you can even save a condition in one graph and load it in another, as long as the model it was encoded for is the one you're sampling with.

One honest caveat before you build your whole pipeline on this: a conditioning is a tensor plus metadata, and it's not portable across model families. A Qwen-Image-Edit condition won't behave like a Flux2Klein one - the text encoder and VAE are different. Load it with the model it was made for, and everything is great. Load it with something else and you'll get garbage or a crash, not a graceful warning.

Install

Part of lrzjason/ComfyUI-EditUtils, installed once per pack - Manager search "ComfyUI-EditUtils" or git clone https://github.com/lrzjason/ComfyUI-EditUtils into custom_nodes, then restart. No pip dependencies, and no model files ship with the pack; the conditioning .ckpt files are ones you create with SaveCondition_EditUtils.

Troubleshooting

The most common surprise is the "No files found" dropdown. The node lists .ckpt files in ComfyUI/models/conditions/ - if you've saved conditions but they're not showing up, check you're looking at the right ComfyUI install's models folder (portable vs. normal installs differ). If a file exists but fails to load, the node swallows the error and returns an empty conditioning, which typically surfaces as a weird blank/black output rather than a loud failure - watch the console for "Error loading condition tensor". And remember the golden rule: the loaded condition still carries its reference latents, so don't load an old cache and expect it to reflect your current reference image.