Boolean

Boolean [RvTools] is a single checkbox that outputs its state as a BOOLEAN. One widget in, one value out, done. You'd think ComfyUI wouldn't need a dedicated node for that, but stock ComfyUI's boolean inputs are usually buried as widgets on the node that consumes them - and widgets can't be wired, shared, or toggled from a group the way a node output can.

Why you'd reach for it

Any time you want one master switch controlling several nodes at once. Wire its output into the boolean inputs of switches, conditionals, schedulers, or any node whose BOOLEAN input is marked as accepting a connection. It's the same trick as the rest of the RvTools primitives: make a value a node instead of a widget so you can fan it out, expose it in a managed group, or flip it with one click when you're testing variants.

It also plays nice with RvTools' own switch logic - if you're building a workflow full of bypassable groups like the author's, a couple of these toggles are how you switch between "pass everything through" and "run the heavy path" without unplugging wires.

How it works

Pure passthrough. The execute method returns whatever the value checkbox holds - default true. Nothing is stored, nothing is computed. The output is typed BOOLEAN, so it only connects to inputs that expect a boolean; if the consumer you're aiming at doesn't accept a wire, look for a way to convert to INT or use an Any-typed switch instead.

Input: value - a checkbox, default on.

Output: boolean - true or false.

Install

Standard pack install:

• ComfyUI Manager → search "RvTools" → install ComfyUI-RvTools_v2 → restart.
• Or: cd ComfyUI/custom_nodes && git clone https://github.com/r-vage/ComfyUI-RvTools_v2, then restart.

No extra models or data files. The pack's requirements.txt pulls in OpenCV and pilgram for other nodes, so a Manager install will grab those too even though this checkbox couldn't care less.

Gotchas

The only real trap is remembering that a primitive node like this is a workflow value, not a setting - if you bypass or mute it, downstream nodes lose their input and may error with a missing connection. And since RvTools v2 renamed everything versus v1, a workflow saved with the old node set won't auto-map to this one. The pack is deprecated in favor of ComfyUI_Eclipse, but a plain boolean primitive is the least likely thing to cause you trouble in any migration.

If you need the reverse - an integer 0/1 that switches behave well with - that's what the RvTools integer primitives are for; this one is strictly for true/false logic.