MultiSwitch (dynamic inputs)

Switch nodes are the unsung plumbing of complex ComfyUI graphs - the thing that lets you swap which model, prompt, or image feeds a branch without rewiring. IAMCCS_MultiSwitch is IAMCCS-nodes' take: five * (any-type) inputs, one output, pick which one flows through. What makes this version worth using over a dozen near-identical switches is what the README touts: it tells you which input is actually active, and you can rename inputs so a five-way switch in a busy graph doesn't read like a wall of input_01.

It's a frontend-quality-of-life upgrade on a commodity idea, from the same pack that brings the big LTX/WAN tooling. For the utility-cabinet part of the pack, this is one of the genuinely useful pieces.

How it works

Five optional input_01…input_05 slots, each accepting anything - MODEL, IMAGE, STRING, LATENT, CONDITIONING, you name it. You select the active one (there's a selector in the node UI), and that input passes through to the single output untouched. Because the type is *, ComfyUI doesn't fight you over what you connect, and the node just relays whatever flows.

The two features that make it a better switch: an active-link indicator in the UI (you can see at a glance which cable is the live one - genuinely useful when you've got five cables into one node), and input renaming. Rename input_01 to "SDXL" and input_02 to "Flux" and the graph suddenly tells you its own story.

Inputs and outputs

• input_01 … input_05 (all *, all optional) - the candidates.
• output (*) - the selected input, passed through.

That's the entire schema. No required inputs, no strength, no mode - it's deliberately dumb, which is the right call for a switch.

How to install

Ships in IAMCCS-nodes. ComfyUI Manager search "IAMCCS", or:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Restart. No extra dependencies, no model downloads. Pack floors: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8.

Gotchas

The * typing is a double-edged sword. It means anything connects - great. It also means ComfyUI can't validate that all five inputs are the same type, so if you switch from a MODEL to an IMAGE mid-graph, the downstream node will error at execution rather than at connect time. Keep each switch to one type and you'll never hit it. Also, five inputs is a fixed ceiling - if you need to swap between six candidates, chain two switches or use one of the bigger any-type routers (this is a small, focused tool, not a replacement for full router nodes). And for anything time-sensitive, remember every switch adds an execution pass; for hundreds of generation iterations the model-comparison use case is where it pays off, not per-frame routing.