Guidance Slider

Guidance is the number that decides whether Flux obeys your prompt or wanders off to do its own thing - and this slider is where the Flux Continuum workflow keeps that control. It's the pack's unified guidance dial: set it once at the front of the workflow and every module reads from it. But there's a twist baked into the pack that surprises people: for inpainting, outpainting, canny, and depth operations, Flux Continuum overrides this slider and forces guidance to 30 automatically.

How it works

Guidance (the Flux-world name for CFG scale) controls how far the sampler extrapolates away from the unconditional prediction. Higher = stricter adherence to the prompt, at the cost of artifacts and saturation; lower = more freedom, but the model may ignore details. The slider ranges from -1.0 to 30.0 with a default of 2.5.

That default is worth a moment, because it's not a typo. Flux is a guidance-distilled model - guidance is trained into the weights, so it runs at low values by default. The KB's standing table for Flux Dev is guidance ~3.5 with Euler and 20–30 steps, and cranking CFG into double digits on a distilled model is how you "burn" an image with doubled render time. 30 is deliberately saved for the one case where Flux genuinely wants it: the BFL fill/canny/depth paths, where a high guidance value keeps the edit faithful to the source structure. Hence the auto-30 behavior.

Inputs and outputs

• value - FLOAT, -1.0 to 30.0, default 2.5, step 0.1. Negative values are allowed (they invert the guidance direction, useful in narrow experiments, useless for most people).

Output is a single FLOAT. It feeds the KSampler's guidance input through the pack's unified control layer, so you don't rewire per module.

Installing it

Part of robertvoy/ComfyUI-Flux-Continuum:

cd ComfyUI/custom_nodes
git clone https://github.com/robertvoy/ComfyUI-Flux-Continuum

or via ComfyUI Manager. Restart after. No pack-specific Python deps; the workflow wants the usual companion packs plus BFL's dev models.

Troubleshooting

The auto-30 override is the thing that will confuse you first. Change the slider to 3.5, run an inpaint, and the node still shows 2.5 while the actual sample runs at 30 - that's by design (the README and the node description both call it out). If your inpaints look aggressively over-guided, that's the pack's choice, not a broken slider. Also watch the negative range: values below 0 are technically accepted but produce garbage on most models, so treat the slider as 0–30 in practice.