DaSiWa Node Status Switch

Every non-trivial ComfyUI graph ends up with parts you want to turn off without deleting them - an alternate upscale path you're A/B testing, a watermark step you only want for final renders, a debug preview you don't need every run. Right-clicking each node one at a time to mute or bypass it gets old fast once you've got more than two or three. This node gives you one toggle that controls as many nodes as you drag into it.

How it works

You add the switch to your graph, then drag an output from any node you want to control into its first target slot. As soon as that slot is filled, a new empty one appears below it - the README describes it scaling up to 99 targets, so in practice you're never actually out of room. Flip the enabled boolean (or feed it from an upstream node) and every target you've wired gets muted or bypassed together, depending on action.

mute versus bypass matters, and it's worth knowing the difference before you pick: muting stops a node from running and produces no output at all downstream; bypassing skips the node's own processing but tries to pass its input straight through as if the node weren't there, which only works cleanly when input and output types line up. If you're toggling something like an upscaler in the middle of a chain, bypass is usually what you want so the pipeline still has something to feed the next node; if you're toggling an entirely optional branch that terminates, mute is fine.

trigger_on flips which boolean state counts as "active" - default is true → active (the switch does its thing when enabled is true), but you can invert it to false → active if that reads more naturally for how you've wired your control logic.

This isn't a new idea in the ecosystem - dashboards for muting and bypassing groups of nodes at once are a well-established pattern (rgthree's Fast Groups Muter/Bypasser is probably the best-known example). DaSiWa's version is per-node rather than per-group, and it's a single self-contained node rather than a toolbar dashboard, which is the tradeoff to know going in: fewer setup steps for a handful of specific nodes, less convenient than a group-based tool if you're managing dozens.

The inputs and outputs that matter

• enabled (BOOLEAN, default true) - the master switch. Wire it from another node's boolean output if you want the mute/bypass state to be conditional on something else in your graph.
• trigger_on - which boolean value counts as "active" for the targets.
• action - mute or bypass, applied to every connected target uniformly.
• enabled_out (BOOLEAN) - the resolved state, so you can chain multiple switches together or feed the state into a display node to confirm what's actually active before you queue a long run.

How to install it

ComfyUI Manager - search DaSiWa-Nodes, install, restart. Manual: clone into custom_nodes, pip install -r requirements.txt, restart. This is a pure logic node - no models, no GPU-specific dependencies, works on anything ComfyUI runs on.

Common issues & troubleshooting

Bypass produces a type error downstream. That's the type-matching limitation above - bypass tries to pass the input through as the output, and if a node's input and output types don't match (a sampler taking LATENT and MODEL but outputting only LATENT, say), bypass can't cleanly substitute. Use mute instead for those, and accept that the downstream chain needs its own fallback for a missing output.

A target didn't get muted. Double check you dragged from the node's actual output slot into the switch, not the other way around - the wiring direction is what registers a node as a target, and it's easy to drag the wrong end on the first try.

Nothing changes when I flip enabled. Check trigger_on - if it's set to false → active and you're expecting true to mean "on," the logic reads backward from what you'd assume.