☁️BizyAir Load Style Model

This is the loader end of Flux's style-transfer / image-variation pipeline, best known by the model it was built for: FLUX.1 Redux. Redux takes an existing image, encodes it through CLIP Vision, and uses that as visual conditioning instead of (or alongside) a text prompt - the result is a variation of the input image rather than something generated purely from words. This node is step one: it loads the style model file itself, ready to be handed to an Apply node.

If you've used Redux locally and found it a bit heavy-handed - the community's early read was that the default workflow "felt like just getting variations of the same image," with the useful range for its strength sitting in a fairly narrow band before it overwhelms the prompt entirely - that's the exact behavior this loader feeds into. How much it dominates is controlled downstream, in whichever Apply node you pair it with, not here.

Inputs and outputs

There's exactly one input: style_model_name, an enum listing the style model files BizyAir has available (the sample shown is flux1-redux-dev.safetensors, Redux's dev checkpoint). Pick it, and the node loads it.

The output is BIZYAIR_STYLE_MODEL - note the custom type. This isn't ComfyUI's stock STYLE_MODEL type, so it only connects to other BizyAir nodes downstream, specifically BizyAir Apply Style Model or BizyAir Apply style model (simple). You can't wire this into a non-BizyAir style-model-apply node, and a locally-loaded style model won't plug into BizyAir's Apply nodes either - the whole chain has to stay inside the pack.

Installing BizyAir

Through ComfyUI Manager: search "BizyAir," hit install. Or clone it manually:

cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git

then restart ComfyUI. Comfy-CLI: comfy node install bizyair. Set your API key before trying to actually load anything - the README calls this out as a required first-use step, reached through a "click to login" link. Because loading here means BizyAir fetching the model server-side rather than you downloading a .safetensors file yourself, there's no local fallback if the key isn't set.

Common issues

If the style_model_name dropdown looks sparse compared to what you'd expect from browsing Redux's model card options, that's normal - BizyAir exposes whatever it currently hosts, which may lag or differ from the full set of community style-model checkpoints floating around HuggingFace.

The type mismatch is the trap most people hit once: this loader's output only speaks to other BizyAir-typed nodes. If your graph editor won't let you connect this to a style-model-apply node you expected it to work with, check whether that node is actually the BizyAir version or a different pack's - they look similar but the types don't cross.

And as with everything else in this pack, a node that loads nothing and throws no obvious error is almost always an API key problem first, a model-availability problem second.