Switch (Seb)

Switch (Seb) is a plain, five-input, any-type switch: set select to a number from 1 to 5 and the matching input flows through to the single output. Image, latent, conditioning, mask, string - doesn't matter, the "any type" wildcard means each of the five input slots will accept whatever you throw at it. It's the ComfyUI equivalent of a radio button, and it shows up in the Seb Nodes pack as a quiet utility node that the README doesn't even mention.

Here's the thing worth knowing before you judge it as "yet another switch": the bundled JavaScript adds a "Mute Inactive" toggle to the node. When it's on, switching to input 3 actually mutes the upstream nodes feeding inputs 1, 2, 4, and 5. Those branches don't execute at all. That's more than cosmetic - it means dead branches can't error, and you're not paying VRAM and compute for chains you aren't using. It's the behavior that makes a bare switch feel like a workflow tool instead of a wire-renamer.

How it works

Python side is trivial: select picks any_input_N and returns it. All the interesting behavior is in js/switch_seb.js, which watches the select widget and toggles the execution mode of connected upstream nodes. The Mute Inactive widget is added by the JS, not the Python schema - it's a UI feature, so if the JS is missing or disabled, you still get a working switch, just without the muting.

Inputs and outputs

• select (INT, 1–5) - which input to pass through.
• any_input_1 through any_input_5 (optional, any type) - the branches to choose between.
• output (any type) - whatever you selected, passed through untouched.

Installing it

Standard pack install, and it's light: ComfyUI Manager → search "Seb" → Install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/cyberhirsch/seb_nodes
# restart ComfyUI

No models, no heavy dependencies.

The honest take

A switch is a switch, and the ecosystem is full of them. If you already run rgthree-comfy, its Any Switch / Context Switch nodes do this and more, and they're maintained through ComfyUI's frontend churn (the KB's panel on rgthree is the place to check the Nodes 2.0 compatibility story). Seb's version earns its slot in one situation: you want the mute-inactive behavior without pulling in a bigger pack. Five inputs is enough for most A/B/C/D/E comparisons, and the muting genuinely speeds up testing - unselected branches just don't run. If your graph has more than five candidates or you need the switch to remember its last selection, go bigger. For a quick "which of these five settings wins" test, this is plenty.