Integer Constant

Integer Constant outputs a single integer. That's the entire job description - you set value, it hands you value back as an INT. There's no compute, no options, no hidden behavior. It's the simplest node in the pack, and if you're the type to dismiss that as pointless, stay with me, because this is the node you end up adding to a graph out of pure convenience.

ComfyUI has primitive value nodes built in, but the workflow pattern that justifies a dedicated integer constant is the shared knob. Feed the same value into several places - a batch size, a steps input, an index - and you get one place to change a number that updates the whole graph. That's real: it turns a magic number buried in three different widgets into a named, single source of truth you can find and edit. It also matters when you want an integer as a wired value rather than a widget you have to reach into - say, feeding a value into Integer Math or a compare node, where wiring from one source is cleaner than retyping it per node.

Inputs and output

One required input: value, an INT with the full signed 32-bit range. One output: value, also INT. The whole range of "settings" is just the number you type.

How to actually use it

The honest answer: wire it into anything that takes an integer and whose value you want to change from one spot. Batch counts, frame indices, step counts, seeds that you want fixed and shared - all good candidates. If you only need a number once, use the built-in primitive and skip this; the node earns its place when the number is reused.

Installing it

ComfyBros installs like any custom node pack - ComfyUI Manager, search "ComfyBros", install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/turnbros/ComfyBros

Then restart ComfyUI. The pack's README is stale and references a requirements.txt that doesn't exist; the actual deps live in pyproject.toml and Manager installs them. Integer Constant lives under ComfyBros/Math.

Gotchas

There's genuinely nothing to break here. The only note worth remembering: this outputs an INT only, so if a node wants a FLOAT, this won't plug in directly - you'd want a float constant from another pack or a quick math conversion. For integer plumbing, it's as close to zero-friction as a node gets.