Logic Comparison OR

WAS Node Suite built its own small logic system before ComfyUI had a native BOOLEAN socket type - values represented as 1 (true) or 0 (false), produced by nodes like Logic Boolean, and combined with a family of gates: AND, OR, XOR, NOT. This node is the OR gate: give it two of those 1/0 values and it's true the moment either input is true, only landing on false when both inputs are false. Per the README's own one-liner for the sibling node, "Logic OR: Given 2 booleans, performs 'OR'" - same operation this node exposes.

How it works

Standard boolean OR, no surprises: at least one input true means the output is true. Only the case where both inputs are 0 produces a 0 result. Because it's WAS's own convention rather than ComfyUI's native boolean, it expects inputs coming from other WAS logic nodes - feeding it a native BOOLEAN type from a different pack may or may not connect cleanly, depending on how strictly that socket is typed.

What it's actually for

Gating something on "any one of these conditions is enough" - run a save step if either a quality check passed or the user explicitly forced saving, without needing both to be true simultaneously. That's the practical difference from the AND gate: AND demands every condition line up, OR only needs one. It's a building block, not something useful in isolation - the output only does anything once it feeds a downstream WAS node that reads that 1/0 as a condition, whether that's a switch node or another logic gate one level up.

How to install it

ComfyUI Manager: search "WAS Node Suite," install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

then, from inside that folder, install requirements - path/to/ComfyUI/python_embeded/python.exe -s -m pip install -r requirements.txt on portable, pip install -r requirements.txt on system Python. Restart ComfyUI; it's under WAS Suite.

Common issues & troubleshooting

If the gate seems to be producing the wrong result, check for a type mismatch before assuming the logic itself is broken - confirm the nodes feeding it are genuinely outputting WAS's 1/0 convention rather than a native BOOLEAN from a different pack that only looks compatible. Mixing WAS's older logic nodes with a newer control-flow pack in the same graph is where this trips people up most; trace each input back to its actual source node when the result doesn't match what you expected.

This is a plain logic node with no dependency of its own, so it's unlikely to break on its own merits. The risk that applies is pack-wide: WAS Node Suite has had no active development since the author marked it retired in December 2023, and the recurring complaint since is the whole suite failing to import after a ComfyUI update - usually because the update quietly downgraded a package WAS still pins for older compatibility. If that hits you, reinstall requirements using your embedded Python interpreter specifically, not a system one.