Recipe Model Picker

Recipe Model Picker (class RecipeModelPicker) is the "choose your model the recipe way" node. Instead of picking a checkpoint and a VAE and a CLIP as three separate widgets, it presents a family-aware selector - pick the model family (SDXL, Flux 1, Flux 2, WAN, Qwen Image, Z-Image, and more), then pick from the models that actually fit that family - and packages the whole choice as one model_data payload for Recipe Relay to write into a recipe. It's the authoring-side counterpart to Recipe Model Loader: that node turns a recipe's model name into real objects; this node produces the structured model choice that ends up in the recipe.

How it works

The type dropdown is the model family - SDXL, Ernie, Flux 1, Flux 2, Qwen Image, WAN Image, WAN Video (i2v), WAN Video (t2v), Z-Image. Everything downstream is filtered by it: model lists only files compatible with the selected family (with sensible folder hints - checkpoints for SDXL, diffusion models for the Flux/WAN families), and vae and clip offer family-compatible options with a (Default) choice that keeps the family's built-in defaults.

The single output is model_data, an ANY-typed payload that feeds Recipe Relay's model_data input. Relay resolves the name, writes the recipe's model fields, and can pass the loaded objects through.

The family awareness is the real feature. In vanilla ComfyUI you can feed a Flux UNet to an SDXL VAE and get a confusing error; this picker constrains you to compatible combos up front. It also does the boring-but-important work of reading your actual installed files for the dropdowns - if you don't have a WAN i2v model, the WAN Video (i2v) picker shows you what you actually have.

Where it fits

It's for building recipes with a hand-rolled graph. The pure recipe flow (Builder → Renderer) picks models inside the Renderer's template and you never touch this node. But when you want a recipe to drive a custom workflow - your own samplers, your own post-processing - you use Recipe Relay as the bridge, and Model Picker is how you hand Relay a well-formed model choice instead of typing a filename and hoping. If you're not using Relay, this node has no consumer and no point.

Installing

Part of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/FranckyB/ComfyUI-Prompt-Manager.git
cd ComfyUI-Prompt-Manager
pip install -r requirements.txt

Or ComfyUI Manager → search "Prompt Manager", then restart.

Gotchas

The model dropdown only populates from models it can identify as belonging to the selected family, and family detection is name-based, so an oddly-named file might not appear even though it'd work. If your model's missing, rename it to something with the family token in the name or check you've got it in the folder the family expects. And (Default) VAE/CLIP means "family default," which is usually right - but if you deliberately want a custom VAE, pick it explicitly, because the default will silently override your preference.