Boolean OR Operator

Boolean OR as a node: two boolean inputs, one boolean output, True if either input is True, False only when both are False. Like its sibling Boolean AND Operator, the node itself is one line of logic. Its value is entirely about what you can express once you have it - "run this branch when any of these conditions is true" is a question you hit all the time in automated workflows, and a single widget can't answer it.

Where it fits

The vsLinx pack's real product is data-driven branching: the Forward/Bypass on Boolean and Forward/Mute on Boolean nodes toggle the state of downstream nodes based on a boolean, and the boolean operators are what let you build conditions instead of just reading one switch. OR is the "any of these" glue. Classic example: a branch should run when the batch is large or when a manual override flag is set - an OR takes those two booleans and produces the single signal the bypass node wants. Paired with AND (both must hold) and Flip (invert a condition), you can compose almost any condition you'd write in code.

It helps that the pack's bypass/mute resolver explicitly walks the upstream graph and understands its own boolean nodes - chain an OR into a bypass input and it resolves correctly, rather than being ignored as an opaque pass-through.

Inputs and output

• boolean_a (default false) - first input.
• boolean_b (default false) - second input.
• Output boolean - True if either is True.

Two boolean widgets, both linkable, one output. Nothing hidden.

Install

Part of the vsLinx pack. ComfyUI Manager → search "ComfyUI vsLinx Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/vslinx/ComfyUI-vslinx-nodes.git comfyui-vslinx-nodes

Restart, find it under vsLinx/boolean. No extra dependencies.

The honest take

Like the AND, this is a "get the set" node - trivial alone, valuable as part of the boolean toolkit that powers the pack's conditional branching. You won't reach for it every day; when you do, it's because a branch needed "any of these" and you'd otherwise be stuck duplicating a condition or giving up and making it manual. Install it with the pack, leave it in the palette, and grab it when the logic calls for it.