🔛✨ Anything Switch On/Off

This is a one-toggle gate you drop into any connection. When the switch is on, whatever you feed in passes straight through. When it's off, the node sends nothing - it effectively unplugs that branch without you having to physically disconnect the wire. In the pack's menu it's "Anything Switch On/Off."

If you've ever found yourself dragging a link off a node to disable it for a test, then dragging it back, this saves you the fiddling. Flip a boolean instead. And because the input type is the wildcard *, it works on literally any data type - images, latents, model, conditioning, text, masks, whatever.

How it works

It's deliberately dumb, which is the strength. Pass-through when on, emit nothing when off. The clever part is what "emit nothing" means for downstream nodes designed to handle it: the author built it to play nicely with the pack's Combine Images node, so an off switch feeding into a combine simply drops that image from the set rather than erroring. So you can wire three images into a combine, put a switch on each, and toggle which ones participate - no rewiring, no broken graph. (There's a text-flavored sibling, "Text Switch On/Off," that does the same for the Combine Texts node.)

The inputs and outputs that matter

• anything - the input, wildcard-typed (*), so any connection works.
• switch - a boolean (default true/on). On passes the input through; off sends nothing.

Output is anything - the same wildcard type, so it slots back into whatever the input was going to.

How to install it

ComfyUI Manager: search Bjornulf_custom_nodes, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/justUmen/Bjornulf_custom_nodes

Restart ComfyUI. This is a pure control node with no dependencies to worry about.

Common issues

The main gotcha is expecting every downstream node to gracefully handle receiving nothing. A node that specifically consumes this pattern - like the pack's Combine Images or Combine Texts - will treat an off switch as "skip this input," which is the intended magic. But if you put the switch in front of a node that requires an input to run (a KSampler that must have a latent, say), turning it off can leave that node with a missing input and stall the graph. Use it where a missing input is meaningful, not where it's fatal.

Otherwise it just works, and it's one of those small quality-of-life nodes you end up using more than you'd expect. Wildcard passthrough means you can leave it in place across very different workflows.