Greater than or equal to

"Greater than or equal to" is the version of the check you actually want half the time, and most people don't realize it until their boundary case is wrong. When you say "run the high-quality pass if the resolution is at least 1024," you don't mean strictly above 1024 - you mean 1024 itself counts. That's >=, and this node is that, wearing a t-shirt. Two numbers in, a boolean out, zero ambiguity.

It's part of marco-zanella's ComfyUI-BooleanExpression pack, a dependency-free logic collection whose arithmetic comparisons all follow the same two-numbers-in, boolean-out shape. This is the inclusive sibling of Greater than, and it's the one that handles "at least" and "minimum" style thresholds correctly.

The inputs

Only two, and both take INT or FLOAT:

• first - the first number (default 0)
• second - the second number (default 0)

Output is result, a BOOLEAN: first >= second. So 5 >= 5 is true here, whereas the strictly-Greater-than node would say false. That one-character difference is the whole reason both nodes exist, and it's the kind of thing that silently eats an hour of debugging if you grab the wrong one.

The natural home for it: feeding a Conditional Branch. "If batch size is at least 4, use the longer prompt" or "if steps are at least 30, enable the detail pass." Because the comparison output is a genuine BOOLEAN, it plugs straight into condition.

Installing it

Same pack, same story: no models, no dependencies, pure Python - the pack's requirements.txt is empty. Install via ComfyUI Manager (search ComfyUI-BooleanExpression) or:

cd ComfyUI/custom_nodes
git clone https://github.com/marco-zanella/ComfyUI-BooleanExpression.git

Restart ComfyUI; the node lives under Boolean Expressions → Arithmetic Comparisons. Fun fact for the searching-inclined: the display name is exactly "Greater than or equal to", but the class name hides a typo - "ArithmenticComparison", an extra n where "Arithmetic" shouldn't have one - so if you ever grep for the class, search for the typo, not the word you'd spell correctly.

Gotchas

• Pick the inclusive one on purpose. > and >= differ only at the exact boundary, and workflows built on "at least X" read better with >=. If your threshold check feels off by exactly one value, this is the node you meant.
• Both branches of any downstream Conditional Branch still compute. A comparison just selects a value; ComfyUI runs both input chains. Cheap for numbers, so don't sweat it here.
• Missing from the menu after install? Restart ComfyUI, and verify the clone landed in custom_nodes. This pack installs cleanly, so that's almost always the fix.

If you find yourself switching between >=, >, =, and friends on the same two numbers, Binary Comparison in the same pack folds all six operators into one node. But for a single, clearly-worded "at least this much" check, this dedicated node is the clearer choice to leave in a shared workflow.