Boolean Group Bypass Controller

Ever built a workflow where you want one switch to enable or disable an entire group of nodes - the detailer pass, the upscaler, the whole img2img branch - without clicking through each node and hitting Bypass? That's this node's job. Boolean Group Bypass Controller takes a boolean from one of the DAELab boolean-list nodes and maps it onto the visual Bypass state of a node group on your canvas.

The name is the spec. It's a controller: it doesn't compute anything, it relays state. You wire a boolean into it, and the pack's front-end turns that true/false into the group's bypass state so the enclosed nodes either run or sit out - the same result as right-click → Bypass, but now driven by a checkbox you can reach from one place (or by another boolean upstream).

How it works

This one is mostly a front-end story. The Python class is nearly empty - a required boolean input, no outputs, OUTPUT_NODE = True - and the source comment calls it a "virtual" node whose execute is only a safe fallback. All the real behavior lives in the pack's web/ scripts, which intercept Active/Bypass/Mute mode changes and apply them to the group. It's a UI affordance, so it doesn't even appear in the normal API prompt. Two things that follow from that: it only makes sense in the DAELab ecosystem (it's designed to pair with Boolean List Hierarchy or Boolean List Hierarchy Get), and it only works with the group features of the pack's app-mode tooling.

The one genuinely clever part is the nested bypass composition. If you have a parent boolean controlling an outer group and a child boolean controlling an inner group, the pack resolves the combination with a bypass-priority rule - an outer bypass wins over an inner active state, and only a fully active ancestor lets a child's state matter. That matches how ComfyUI already treats nested groups, just with boolean ancestry standing in for manual clicks.

The input that matters

• boolean - the switch. Wire it to any BOOLEAN output of Boolean List, Boolean List Hierarchy, or Boolean List Hierarchy Get. Note it's forceInput, so you can't just set a literal value on the node - you have to actually wire a boolean in. That's deliberate: the whole point is that this state comes from somewhere upstream.

How to install it

Part of the DAELab pack. ComfyUI Manager, search "ComfyUI-DAELab-Custom-Nodes-Library", or:

cd ComfyUI/custom_nodes
git clone https://github.com/TeutonicMepheles/ComfyUI-DAELab-Custom-Nodes-Library

then restart. No models, no extra dependencies. Because the behavior is front-end, make sure you cloned the whole repo - the web/ directory is what actually loads the controller - and don't leave old scattered copies of these nodes around, or the pack may refuse to register on duplicate IDs.

Common issues & troubleshooting

"The node does nothing when I toggle it." Check three things: you're in a workflow that the pack treats as an app (the group/bypass composition is part of app-mode), the boolean is actually wired in (forceInput means an unwired input is a non-starter), and the node isn't muted - a muted virtual node won't pass state through.

"It works but my group isn't bypassing." The controller maps onto node groups on the canvas. If your nodes aren't inside a group (or you're using a different group feature), there's nothing for it to drive.