ComfyUI Client Set Float (Yogurt Nodes)

Same idea as its int sibling, one type up: ComfyUI Client Set Float patches a floating-point input on a remote workflow before it runs. denoise, strength, cfg-adjacent decimals, start_percent/end_percent - anything the remote graph takes as a float. You name the node, name the input, drop a value on it, and the client carries the patch through to Run.

Why you'd use it over Set Int

Floats are where the fine control in a diffusion pipeline lives. The single most useful case is a local UI that drives a remote generation: you keep a slider in your local graph for denoise, Set Float injects it into the remote workflow's sampler, and Run fires the job - you get a control panel on one machine for a GPU on another. Or the value can be computed locally: scale your denoise by image count, clamp a strength based on a logic branch, and ship the result. That's the real payoff of the Set nodes generally, and floats are the flavor of it that shows up in sampler parameters most often.

Like all the Set nodes, it chains: each one takes the COMFYUI_CLIENT, patches it, and passes it out for the next patch or for Run.

Inputs

• client - the handle from Load or a previous Set node.
• node - the remote node's id or title.
• key - the input field name, exactly as in the workflow JSON.
• value - the float to write. The schema gives it a default of 0, but the whole point is that you're wiring this from a Float node or a slider, not leaving it.

Outputs

• client - the patched handle, ready for the next node.

Install

Standard Yogurt Nodes install. ComfyUI Manager → search "ComfyUI-YogurtNodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/yogurt7771/ComfyUI-YogurtNodes.git
cd ComfyUI-YogurtNodes && pip install -r requirements.txt

Then restart ComfyUI.

Where people get burned

Same class of silent failure as Set Int, with one extra wrinkle: float precision and range. If the remote input is a float with a defined min/max (ComfyUI widgets carry those), writing a value outside the range can get clamped or rejected depending on how the server handles it - check the remote widget's limits if your extreme value doesn't stick. And the type boundary matters more than it looks: some remote inputs are stored as floats but display as ints, and some ComfyUI widgets are actually combos whose backing values are floats. If patching denoise works but patching something that looks numeric doesn't, it's a combo, not a float - that's a Set String job. When in doubt, read the workflow JSON; the input's type field never lies.