Boolean

Komfy_Boolean is the simplest node in the HMT Suite pack: a checkbox with a true/false value that comes out the other side as a BOOLEAN wire. You flip it, something downstream reacts. That's the whole job, and it's honest about it.

Why does such a nothing node exist? Because booleans are the least convenient thing to wire in ComfyUI. Most switch and gate nodes take a boolean input, but the value usually lives as a widget buried on another node - so you end up right-clicking, converting widget to input, and hunting for the source. A dedicated Boolean node gives the switch its own place in the graph, one you can retitle and find again.

How it works

Nothing up its sleeve: one required input, value, a BOOLEAN defaulting to true; one output, also value. The output is a proper typed BOOLEAN socket, so it plugs into any node expecting a boolean - a switch, a gate, an if-node, a sampler toggle - without conversion tricks. The node re-executes every run, which for a value node is exactly what you want: flip it, queue, and the change flows through immediately.

Where you'll use it

The classic pattern is a single switch driving several consumers - think of it as "one source, many consumers" from the plumbing playbook:

• Enable or bypass a whole processing branch through a switch node.
• Toggle a detailer or upscaler on and off without editing two widgets in different places.
• Gate something in and out of a run based on one checkbox.

Because the label comes from the node title (that's the "Komfy" convention), retitle it to something meaningful - Detail pass? - and your graph reads like a sentence instead of a wiring diagram.

Install

It's part of the whole HMT Suite pack:

cd ComfyUI/custom_nodes
git clone https://github.com/tuyenhm68/ComfyUI-HMT-Suite.git
cd ComfyUI-HMT-Suite
pip install -r requirements.txt

Restart ComfyUI and it appears under HMT Suite > Komfy > Boolean. (In Manager, search "ComfyUI-HMT-Suite".)

The honest take

ComfyUI core ships PrimitiveBoolean, which does the same thing, so this node is only worth your sockets if you're already on the HMT pack for its downloader and updater nodes - and at that point it's a fine, zero-cost convenience. It's not the node to install a pack for. What it is good for: forcing yourself to wire booleans explicitly instead of leaving a toggle hidden on a random node, which genuinely makes messy workflows easier to read.