☁️BizyAir CFGGuider

If you've ever wired up ComfyUI's "advanced" sampling nodes - SamplerCustomAdvanced, a Noise node, a Sigmas node - you've met the concept of a Guider even if you didn't know the name. A Guider is the object that tells the sampler how to steer each denoising step toward your prompt. CFGGuider is the classic implementation: classifier-free guidance, the same mechanism behind the plain "CFG" slider on a normal KSampler, just packaged as a swappable node instead of baked into a monolithic sampler. BizyAir's version does the exact same job, except the model, positive and negative conditioning it operates on all have to come from BizyAir's cloud loaders - this node ships nothing to your GPU, it calls SiliconFlow's BizyAir service and hands back a GUIDER object.

That last part is worth sitting with. Every input here - model, positive, negative - is typed BIZYAIR_MODEL / BIZYAIR_CONDITIONING, not the plain MODEL / CONDITIONING you'd get from a stock Load Checkpoint node. That's ComfyUI's type system doing its job: you can't accidentally wire a locally-loaded checkpoint into this node, because the wire simply won't connect. Everything upstream of a BizyAir_CFGGuider - checkpoint, CLIP, conditioning - needs to be BizyAir nodes too. The one place this loosens up is right here: the output is plain GUIDER, not BIZYAIR_GUIDER, so it plugs straight into a completely normal, stock SamplerCustomAdvanced alongside whatever sampler and sigmas node you'd use anywhere else.

Inputs that matter: model, positive, and negative are just wires from your BizyAir checkpoint/CLIP chain - nothing to configure. cfg is the one dial: a float, default 8, range 0–100. That default is straight out of the SD 1.5/SDXL era, where 5–9 is the sane range and 7 is the textbook default. If you're pointing this at one of BizyAir's newer catalog models - anything guidance-distilled, which by 2026 is most of what's shipping - leave cfg near 1. Distilled models have the CFG correction trained into their weights already; running them at 8 applies it twice, doubles your render time, and burns the image (oversaturated, crunchy, "deep fried"). If your renders look overcooked, that's the first thing to check, and it's an easy trap to fall into precisely because the node's default hasn't caught up with where the model landscape moved.

How to install it: search "BizyAir" in ComfyUI Manager and hit install, or cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git and restart, or comfy node install bizyair if you're on the Comfy CLI. Any of the three gets you the whole pack, not just this node - there's no way to install a single BizyAir node in isolation. Then, before anything will actually run, register an account at BizyAir's site and drop your API key into the node's first-run login prompt. Skip that step and every BizyAir node in your graph - this one included - just fails.

Where people get stuck: the most common complaint isn't the guider itself, it's the chain around it. If a downstream sampler errors with a type mismatch, you've got a stock node feeding into (or reading from) this one somewhere - trace the wire back. If the whole run stalls partway with a vague failure notice from BizyAir rather than a clean ComfyUI error, that's usually the cloud call itself failing (bad or missing API key, or a hiccup on SiliconFlow's end) rather than anything wrong with your graph. And if you inherited a workflow with BizyAir nodes in it and never installed the pack on purpose - it happens, older versions of ComfyUI Manager sometimes auto-installed BizyAir when guessing at missing nodes - you can safely remove it from Manager if you don't want a cloud dependency in your workflow at all.