easy int

It's a box that holds one whole number and outputs it. That's genuinely all it is, and the reason it earns a spot in your graph is that a single named integer, sitting in its own node, is worth more than the same number typed into a widget somewhere. When one value - steps, a batch size, a width, a loop count - feeds several places in a workflow, you want one source of truth for it. Change it once, and everything downstream updates. That's easy int.

Why you'd reach for it

Two situations, mostly.

The first is shared constants. Say three nodes all need to agree on "512." Type it into all three and you now have three places to update and a standing chance of forgetting one. Drop an easy int set to 512, wire it into all three, and there's a single dial. This is the same discipline as pulling a magic number out into a named variable in code.

The second is feeding logic. The EasyUse/Logic family - the math nodes, the index switch, the for-loops - runs on integers. easy int is the clean way to inject a literal into that machinery: a starting index, a divisor for easy mathInt, the count a switch picks from. It gives the number a node of its own so it's visible, labelable, and easy to reconnect.

It's deliberately minimal. If you need the value to change per run, that's what a seed node or a math node is for; easy int is the fixed literal.

The inputs and outputs

There's one control and one output:

• value (INT, default 0) - the number, adjustable from -999,999 to 999,999. Type it, or convert it to an input socket and drive it from something else.
• int (INT output) - the value, handed to whatever you wire it into.

No modes, no options. A number in, the same number out, as a proper INT type that any integer socket will accept.

Installing it

ComfyUI Manager: search ComfyUI Easy Use, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

then install the requirements (install.bat on Windows, else pip install -r ComfyUI-Easy-Use/requirements.txt) and restart. No models, no dependencies to worry about - it's a primitive.

Common issues

Honestly there's very little to go wrong, but two things come up:

• INT is not FLOAT. This outputs a strict integer. If a target socket wants a float (a cfg value, a denoise strength), it may refuse the connection - reach for a float primitive there instead. Conversely, some nodes silently truncate a float you feed them, and easy int is the honest way to be explicit that you meant a whole number.
• The range caps at ±999,999. Fine for essentially every generation parameter, but if you're doing something exotic that needs a larger literal, note the ceiling. (For big-number math, easy mathInt handles a far wider range.)