StyleModelClamp

StyleModelClamp takes a STYLE_MODEL in and hands the same STYLE_MODEL back. No style transfer happens here, no weights get touched - it's a pass-through. But of all the clamp family, this is the one that earns its keep, because STYLE_MODEL is a wire most people barely ever see.

What it's for

STYLE_MODEL is a niche type. You meet it when doing style-transfer style workflows - the StyleModelApply node takes one alongside your conditioning to steer a generation toward a reference image's look. It's not a core wire like MODEL or LATENT, it has no preview, and it appears in exactly one or two places in a graph. So when it's in your workflow at all, it's easy to lose track of which one is which, and there's nothing on the wire to tell you.

StyleModelClamp gives that wire a labeled, selectable home. Title it after the style it carries, and the graph becomes readable at a glance. It's also a clean branch point if one style model feeds multiple apply nodes, and a stable anchor to hang a debugger on. Same idea as a reroute - making an unruly graph navigable - but for an object type primitives can't hold.

How it works

The implementation is def node(self, style_model): return (style_model,). The identical object flows out - no copy, no transform, no measurable cost. It's one of 13 pass-through clamps in Allor's "clamp" family (MODEL, VAE, LATENT, IMAGE, MASK, CONDITIONING and friends all get one), so the habit carries across your whole graph.

Input: style_model (STYLE_MODEL, required). Output: STYLE_MODEL. That's the whole interface.

Installing Allor

StyleModelClamp lives in the Allor Plugin, Nourepide's ~90-node image-processing pack. Install via ComfyUI Manager (search "Allor") or:

cd ComfyUI/custom_nodes
git clone https://github.com/Nourepide/ComfyUI-Allor

Restart ComfyUI. First run creates a config.json in the pack folder; the bundled install.sh / install.bat install requirements into your venv or embedded Python. The pack's dependencies (rembg, onnx, plus onnxruntime via rembg) exist for its segmentation nodes - this pass-through doesn't touch them.

Common issues

The pack's known pain point is updating. Its history was rebased to strip image files, the README warns auto-updates can break, and users report Allor nodes silently vanishing after an update. A fresh re-clone is the reliable fix; "update_frequency": "never" in config.json sidesteps it.