Boolean

Boolean is the least glamorous node in ComfyUI_Eclipse: one checkbox, one output, nothing else. It exists because the alternative - typing the same True into six different widgets and praying you update them all together - is how you get a workflow that runs a completely different configuration than the one you think you saved. A value node breaks the value out of the widget and makes it something the graph can fan out from a single socket. Flip it once, and every consumer updates.

How it works

You set value (default True), and the node outputs a boolean. The implementation is deliberately defensive: if it somehow receives something that isn't a Python bool, it defaults to True rather than crashing. That's it. There's no state, no seed, no hidden behavior.

What you wire it into

The output plugs into anything that takes a boolean input:

• Switches - an Any Dual-Switch or the Input selector on Eclipse's router nodes can be driven from a boolean so you flip behavior from a single checkbox instead of editing a number.
• Conditional execution - feed it to an If Execute or any node with a converted-to-input boolean widget to gate a branch on a condition you can toggle while iterating.
• Purge toggles - the Purge_VRAM flag on Eclipse's Switch/Purger nodes is exactly this shape: one boolean, one source, one place to change your mind.

The Boolean Passer variant exists for the cases where you want to route that value around a graph and have it default to False when nothing is connected - useful, but if all you need is a source of truth for a true/false, this is the node.

Installing it

Part of ComfyUI_Eclipse, so install the pack once:

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

Restart ComfyUI, or use ComfyUI Manager and search "ComfyUI Eclipse". It's pure Python with no dependencies beyond the standard library.

Gotchas

Not much to trip over with a checkbox. The one pack-wide thing worth knowing: ComfyUI_Eclipse was formerly RvTools, and v4.0.0 deleted all the legacy nodes. If you load an old workflow, the Workflow Migration Tool node (or python tools/migrate_workflow.py <workflow.json>) will rewrite the old IDs with a backup.

The deeper point is that a boolean is only as good as the logic around it. It's the primitive that feeds every switch and gate in your graph - the plumbing layer that's 70% of any workflow you actually run. Boring, invisible, and the reason the flashy nodes can do their job.