easy boolean

easy boolean is a single on/off toggle that outputs true or false. That's the whole node. It exists because ComfyUI's logic nodes - the if/else branches, the switches, the gates - need boolean inputs, and it's cleaner to have one clearly-labeled toggle you can flip than to convert an integer or fish a boolean out of somewhere else. It's the smallest building block in Easy-Use's Logic/Type family, and it's the thing you wire into everything else in that family.

If you've ever wanted a master switch in a workflow - "run the upscale pass: yes/no", "enable the detailer: yes/no" - this is the switch. You flip it once, and its output drives a gate or an if/else downstream.

How it works

There's no logic inside it. It holds one value, value, and emits that value as a BOOLEAN. The intelligence lives in whatever consumes it - an easy ifElse, an easy blocker, a switch node. easy boolean just gives you a hard, obvious place to set the flag, instead of that decision being buried as a widget on some other node three screens away.

The input and output

• value - the toggle, defaulting to false. Click it on for true.
• Output: boolean (a BOOLEAN). Wire it to any node that takes a boolean.

That's it. Nothing to misconfigure.

How to install it

Via ComfyUI Manager: search "ComfyUI Easy Use", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

Then install.bat / pip install -r requirements.txt, restart. Preinstalled on comfy.icu.

Common issues

There isn't much to break here, so the "issue" is really about knowing what to pair it with. A boolean on its own does nothing visible - it only matters when something reads it. If flipping this toggle seems to change nothing, the question is downstream: is it actually wired into a gate or branch, and does that gate actually control the path you think it does?

The one genuinely useful pattern worth calling out: pair easy boolean with easy blocker to build a manual kill-switch for an expensive branch. Set the boolean false, wire it to the blocker's continue, and that branch of the graph simply won't run until you flip the switch to true. It's the tidiest way to keep a heavy optional step (a big upscale, a second sampler) in your workflow without paying for it every single run. Default false is a sensible starting state precisely because you usually want the optional thing off until you ask for it.