Int Value (CRT)

This is the most boring node in the pack, and it's also the one you'll quietly rely on. Int Value (CRT) takes a single number you type in and passes it out as an INT. That's the whole job. No math, no transforms, no secret sauce - one integer in, one integer out.

So why does it exist? Because ComfyUI's stock value widgets are widgets, not outputs. When you want a batch-size number, a frame count, or a seed to be driven by something else in the graph - another node, a math node, a widget that other nodes also read - you need the value exposed as a real connection. That's what this node is for: it turns "a number" into "a number on a wire," which is the currency of a graph that has to stay consistent when you change one setting and expect three downstream nodes to notice.

The input is a plain INT with the full 32-bit range (-2147483648 to 2147483647), defaulting to 0. The output is an INT. That's the entire spec sheet.

How you'd actually use it

The classic pattern is a shared control: put one Int Value on the canvas, set it once, and wire its output into anything that needs that number. Change it in one place and the whole graph follows - instead of hunting for three separate widgets that all say "16" and hoping you updated them all. Workflow authors use this exact trick so that the person receiving their exported graph has a single obvious "batch size" control instead of a dozen scattered fields.

It's also the natural partner for CRT-Nodes' own batch and sampler nodes, where a feedable INT is more useful than a buried widget.

Install

It ships inside CRT-Nodes, so you install the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/PGCRT/CRT-Nodes.git
pip install -r CRT-Nodes/requirements.txt

Restart ComfyUI (or use ComfyUI Manager and search CRT-Nodes). You'll find it under CRT/Utils/LogicValues.

Troubleshooting

Honestly, there's nothing to break. The only "issue" is conceptual: people expect a primitive node like this to do something clever and then reach for it in situations where a widget would've been simpler. If you're not wiring the output anywhere, just use the widget. If you are feeding it into other nodes, remember the output is a plain Python int, so it plugs into any INT input - and if a target node's range is narrower than yours, clamp the value on this node before connecting, because ComfyUI will happily pass a 5000000 into a node whose slider caps at 4096 and then yell at you about validation.

You'll never show this node off. But when a workflow has a dozen places that need to agree on one number, it's the difference between a five-minute edit and a full afternoon of remembering where you left the number.