ConditioningClamp

ConditioningClamp is Allor's pass-through node for CONDITIONING data. In goes a conditioning, out comes that exact same conditioning, untouched. It's a no-op with a one-line schema - conditioning in, CONDITIONING out, no parameters - and it belongs to a family of identical clamps (CLIP, CLIP_VISION, ControlNet, GLIGEN, MODEL, MASK, LATENT) that all exist to solve the same unglamorous problem: keeping big graphs readable and their execution order predictable.

Conditioning is the encoded text-plus-metadata object that CLIPTextEncode produces and the KSampler consumes - the thing that actually tells the model what to draw. In a simple workflow it's a straight wire from the encoder to the sampler, and you'll never think about it. But the moment you have two samplers, an unCLIP pass, or any of the million variants where one encoded prompt feeds several downstream stages, you start wishing the wire didn't cross the whole canvas.

Three genuinely useful jobs for a pass-through here:

• Splitting one conditioning to many consumers. Feed a single CLIPTextEncode output through ConditioningClamp and fan out from its output. No wire tangle, and the split point is explicit in the saved workflow.
• Forcing order. The clamp creates a real dependency edge, so consumers downstream of it are scheduled after it. When you're fighting a graph where a branch computes before you expect it to, that forced ordering is a free, predictable lever.
• Keeping shared workflows legible. "Workflow included" culture means other people will load your JSON. A named clamp communicates intent - "conditioning branch here" - far better than a wire disappearing off-screen.

Installing it

It comes with the Allor plugin:

cd ComfyUI/custom_nodes
git clone https://github.com/Nourepide/ComfyUI-Allor
cd ComfyUI-Allor
pip install -r requirements.txt

Restart ComfyUI, or install "Allor" from ComfyUI Manager. Pack gotchas worth knowing up front: the requirements.txt drags in rembg and onnx for the segmentation nodes even though this clamp needs neither, and Allor's repo was rebased to strip all images from git history (a ~344x size cut) - a change that can make auto-updates fail. When they do, the docs at nourepide.github.io/ComfyUI-Allor-Doc have troubleshooting pages for both update paths.

Real talk

ConditioningClamp is a glorified wire, and it knows it. Don't add it to a workflow that's working - you'll just be adding a node that does nothing. Reach for it when the graph outgrows you: when one prompt feeds many samplers, when execution order starts feeling spooky, or when you're about to share a workflow and want the branches labeled. It's boring on purpose, and that's the whole appeal.