Nodes/ComfyUI vsLinx Nodes/Boolean AND Operator
ComfyUI Node

Boolean AND Operator

Boolean AND Operator — two conditions, one true

By vslinx·Created about a year ago·Updated 26 days ago· 25
Boolean AND Operator
    • boolean
    boolean_afalse
    boolean_bfalse

    Boolean AND, as a node: two boolean inputs in, one boolean out, True only when both inputs are True. In isolation that's the most boring node imaginable - a one-line Python expression. In a workflow, it's what turns "either of these things" into "both of these things", and that's how you build conditions that actually mean something.

    Where it earns its keep

    ComfyUI's native way to switch branches is manual right-clicks. The vsLinx pack's contribution is making those switches data-driven, and the boolean operators are the connective tissue. Wire an AND into the bypass input of Forward/Bypass on Boolean (Any) or the mute input of Forward/Mute on Boolean (Any) and you get a branch that only activates when every condition holds: "only run the hires fix when the batch is large and the quality flag is on." A single boolean widget can't express that. An AND can.

    It also composes with the pack's own Boolean Flip (invert a condition before ANDing) and Boolean OR (either/or), so you can build real boolean logic in the graph. And it matters that the pack's bypass/mute resolver walks the upstream graph - it explicitly recognizes its own AND/OR/Flip nodes, so a chained expression resolves correctly instead of silently ignoring the operator.

    Inputs and output

    • boolean_a (default false) - first input.
    • boolean_b (default false) - second input.
    • Output boolean - True only if both are True.

    Both inputs are plain boolean widgets, linkable from any boolean source. 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

    This is a "get the set" node. On its own it does one trivial thing; the value is that it's one of the small parts that make the pack's bypass/mute branching actually powerful. If you're only ever toggling branches by hand, you don't need it. The moment you want a branch that responds to two conditions at once - which is most real automation - you'll be glad it's there. Expect nothing more than the truth table it advertises, and use it exactly for that.

    CategoryvsLinx/boolean

    Inputs (2)

    NameTypeDefaultDescription
    boolean_aBOOLEANfalse
    boolean_bBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    booleanBOOLEAN