hswq_ComboClone

Everything in ComfyUI that's worth broadcasting is a socket - except the things that are dropdowns. Sampler name, scheduler, checkpoint filename, LoRA filename, upscale method: all widgets, no socket, so Use Everywhere had nothing to grab. hswq_ComboClone is the workaround, and it was the most-requested feature in the pack's history - the author shipped it as the headline of Use Everywhere 7.2 in October 2025.

The node's own description is the whole manual: "The combo on this node will replicate whatever the output is connected to."

How the cloning actually works

Connect comboout to a combo widget on another node - drag the output onto a dropdown, not a socket. On that connection the frontend reads the target widget's option list, snapshots it into the node's stored properties, and rewrites its own dropdown to hold the same values with the same type (COMBO). The node's dropdown label even takes the target input's name, so you can see at a glance what it's mirroring.

Then the value on this node is a combo it can actually broadcast, because the output is a real socket. From there it behaves like anything else in the family: every matching unconnected combo in the graph gets filled at queue time, and your canvas keeps looking tidy.

Why bother? Because a workflow with four loaders that all need the same checkpoint is four dropdowns you have to keep in sync by hand, and you will forget one. One clone plus a broadcast, and the value exists once.

There's a second, less obvious route to the same place: the Use Everywhere properties on any node include a string_to_combo flag, which lets a broadcast STRING feed combo widgets directly. If you're driving combos from a string source, check that before reaching for a clone.

Inputs and outputs

combo is the only input and it's required - a single-select widget whose option list starts as the placeholder connect me to a combo widget until you wire it. The output comboout is typed * in the schema and narrows to COMBO once the link is made.

Two hard rules the frontend enforces, which is why it sometimes feels like the node is refusing you: the output will only connect to a COMBO input or to another Use Everywhere node. Drop it on a numeric widget or an IMAGE socket and nothing happens - no error dialog, just no link. That's deliberate; a clone of a non-combo is meaningless.

Where people get caught

The snapshot is taken at connect time. Add a new checkpoint to models/checkpoints and the clone's dropdown won't necessarily know about it until you disconnect and reconnect, or reload the workflow - the stored option list is what it restores from on load. Same story if you point the clone at a different node: it re-reads and replaces, it doesn't merge.

And the broad one, which applies to the whole family: the connection from your clone to its four consumers lives only in the executed prompt, not in the workflow file. Share the graph and the clone arrives with its dropdown intact and no visible link to anything.

Install

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

Restart ComfyUI; the node lives under the everywhere category. It's part of a port of chrisgoringe/cg-use-everywhere merged into this pack - the hswq_ prefix keeps its class types from colliding with the upstream install, so don't run both.

The pip install is heavier than these nodes deserve: requirements.txt drags in nunchaku, the Florence-2 libraries and a TensorRT-RTX stack for the pack's CCSR upscaler, and the pack imports all of its submodules at startup. Skip it and you can end up with the entire pack missing rather than just one broken node. There's no GPU or model download involved in any of the Use Everywhere nodes, though - ComfyUI starting up is the whole dependency.

Quick sanity check

If the dropdown on your clone still reads connect me to a combo widget, the output isn't attached to a real combo input. If it cloned once and now offers the wrong list, your models folder changed since. If the value never shows up downstream, the receiving combos are either already wired, or another broadcaster is claiming them at equal priority - the properties editor shows the regex restrictions that will win that fight.