int _O

int _O is a single integer input that hands its value to whatever you wire it into. That's the whole node, and it earns its place by being the boring, reliable answer to a real workflow problem: you've got a number you keep retyping - steps, batch size, a seed, an index - and every copy is a place to introduce a typo.

It lives in the O/utils folder of omar92's Quality of Life Suit pack, next to float _O, Text _O, and seed _O. The pattern is the same across all of them: a plain widget exposed as a typed output so a value has one home in the graph instead of being scattered across a dozen identical widgets. That's the "quality of life" the pack is named for - nothing fancy, just less fiddling.

How it works

Pass-through, full stop. The source returns the int input unchanged as an INT. No rounding (you can't type a decimal into an INT widget anyway), no clamping that matters.

• int (INT) - the value. Default 0, widget range 0 to a very large max.

One input, one output. If you can count, you can use this node.

Where it fits

The genuinely useful version of this is the shared-parameter pattern: set int _O to 30, wire it to both a KSampler's steps and any other node that wants the same count, and changing one widget updates the whole graph. It also plays nicely with the pack's math nodes - Equation2params _O takes x and y as FLOAT, so run int _O through the conversion chain if you want to compute a value from an integer.

Where it doesn't fit: single-use numbers. If only one node needs the value, just use that node's own widget. The utility node pays for itself when the value is shared or when you want the graph to show your "settings" clearly in one spot.

Installing it

Part of the Quality of Life Suit pack (omar92/ComfyUI-QualityOfLifeSuit_Omar92). Install via ComfyUI Manager (search "Quality of Life Suit") or clone:

cd <ComfyUI>/custom_nodes
git clone https://github.com/omar92/ComfyUI-QualityOfLifeSuit_Omar92.git

Restart ComfyUI properly. No models, no dependencies. Worth knowing: the pack's config.json defaults autoUpdate to true, so it may pull new commits from GitHub on startup - set it to false if that behaviour surprises you.

Common issues

• "The downstream node shows a different number." Pass-through nodes don't corrupt values. If an INT reaches a node that expects FLOAT, check whether you skipped a conversion - some nodes will accept the wrong type and quietly behave oddly.
• "I want negatives." The widget slider starts at 0, but you can type a negative in. Works fine.
• "It's not that interesting." Correct. That's the design brief.

It's the kind of node you'll install once and forget exists - which, for a value holder, is exactly the right outcome.