GligenClamp

GligenClamp is Allor's pass-through node for the GLIGEN data type - the object you load with GLIGENLoader and feed to a GLIGENTextBoxApply node to pin specific objects to specific box regions in the frame. It takes a gligen input and hands back the identical GLIGEN object, unchanged, with no parameters to fiddle with.

Let's be honest about the context: GLIGEN is the niche member of ComfyUI's model zoo. It lets you say "person on the left, couch on the right" by literally drawing bounding boxes, and it's genuinely clever - but it's also an extra download for a feature most people reach for once and forget. If you're not running GLIGEN workflows, this node is irrelevant, and that's fine. If you are, the clamp is useful for the same reasons every clamp in this family is:

• Splitting. One loaded GLIGEN model feeding multiple box-apply nodes gets a clean, visible fan-out point instead of a wire stretched across the canvas.
• Forced execution order. A pass-through creates a real dependency edge, so anything downstream of the clamp is guaranteed to run after it. In a graph where the GLIGEN loader and its consumer race, that's a free deterministic ordering point.
• Readability. If you're sharing the workflow (the norm in this community), an explicit named node shows future readers where the GLIGEN branch lives.

The schema is as small as it gets: gligen in, GLIGEN out. Nothing to tune, nothing to break.

Installing it

It's part of 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 search "Allor" in ComfyUI Manager. Expect two pack-level quirks: the requirements.txt installs rembg and onnx for the segmentation nodes even though this clamp needs neither, and Allor's repo was rebased to strip all images from its git history (a ~344x size cut), which can make auto-updates fail - the docs at nourepide.github.io/ComfyUI-Allor-Doc have troubleshooting pages for exactly that. The GLIGEN model file itself isn't bundled; load it the normal way with ComfyUI's GLIGENLoader.

Real talk

GligenClamp is a wire with a name. If your GLIGEN workflow works, you don't need it. But GLIGEN workflows are exactly the kind that get messy - boxes, conditioning, multiple applies - so the moment one shared model feeds several box nodes, dropping in the clamp will save you the part of the session you'd otherwise spend tracing wires. It's boring, and that's the appeal.