Boolean Passer

Boolean Passer routes a boolean through your graph, with one behavior that makes it quietly valuable: when the input is disconnected, muted, or bypassed, it outputs False. Most passers pass None through when nothing feeds them. This one turns "nothing" into a definite, safe value - and that tiny difference is why you'd reach for it over the generic Any Passer in logic-heavy graphs.

Why the False-default matters

ComfyUI's convention is that unconnected optional inputs arrive as None. For a boolean that's awkward, because downstream logic usually wants a decision, not a shrug. If you've built a conditional branch that does "if this flag is on, do the extra pass," a None where the flag should be can silently change the outcome - or worse, crash a node that expects a strict bool. The Boolean Passer kills that class of bug: disconnected means off, full stop.

There's a real workflow pattern behind this. You convert a widget on some node "to input," wire a boolean source into it, and then want to route that flag around the graph - maybe fanning it to two consumers, or carrying it through a subregion. When you later mute or bypass the source (a common way to test a workflow without the flag), this passer makes sure the downstream logic sees False rather than a spurious None. The tooltip says it straight: "Outputs False when the input is muted or bypassed."

How it works

A single optional BOOLEAN input, force_input, so you can wire a Boolean node into it or convert a widget. The execute logic is one line: pass the input if it's not None, otherwise emit False. No state, no caching tricks, nothing clever.

Inputs and output

• input - the boolean to pass through (optional; unconnected → False).
• Output - output, a BOOLEAN.

Where it sits in the family

Eclipse's typed passers each enforce a type - this one enforces BOOLEAN and adds the safe default. If you don't care about the safe-default behavior, the Any Passer will carry a boolean too. But for gating logic - feeding a switch's selector, an If Execute, a Purge_VRAM flag - the guaranteed-False output is the difference between a branch that reliably turns off and a branch that occasionally does something surprising.

Installing it

Part of ComfyUI_Eclipse, installed once:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart ComfyUI (or ComfyUI Manager → search "ComfyUI Eclipse"). No extra dependencies.

Gotchas

The pack-wide note: ComfyUI_Eclipse was formerly RvTools, and v4.0.0 removed all legacy nodes - old workflows need the Workflow Migration Tool node (or python tools/migrate_workflow.py <workflow.json>) to rewrite old IDs with a backup. And the one thing to internalize: the False-on-nothing behavior is intentional, so don't treat "the value went False" as a bug when you bypass the source - that's the node working as designed.