int+

The name is a lie in the best way: int+ (class INTPlus, from the LumyINTP pack) is not an AI anything. It's ~70 lines of Python plus a sliver of frontend glue, no model download, no API key, no dependencies. It exists to solve one annoying problem - an integer that changes on its own, but only when you want it to.

It was literally born from a reddit request. In January 2026 someone on r/comfyui wanted to save an image at each step of a workflow with the run number in the filename, but pause that counter while they tested changes. ComfyUI 0.8.2 had just broken their bypass-based workaround, and ComfyUI's built-in INT widget is a constant - it can't count. So the pack's author built exactly that and shipped it. If you've ever wanted a "run number" node that behaves, this is the thing.

The one trick it does

A stock INT primitive holds whatever number you type. INTPlus is a stateful integer: on every execution it can keep the value, add one, subtract one, or roll a random seed - and a signal input decides whether any of that happens at all. Wire anything into signal (the input accepts any type) and the mode only applies when the signal is "active." If the signal is None or False, the node treats it as inactive; anything else - a real value, a True boolean - counts as active. Flip the invert toggle and the logic reverses, so control happens when the signal is off.

The inputs that matter

You'll set three of the four, most of the time:

• int - your starting value. Default 0, bounded at roughly ±1.1 quadrillion with wrap-around, so it won't overflow into nonsense if you leave it counting forever.
• control_mode - fixed (never changes - effectively a plain primitive), increment (+1 per active run), decrement (−1), or random_seed (rolls a fresh value between 1 and max every active run).
• invert - flips which signal state triggers the mode.
• signal (optional) - the gate. This is the input that makes the node interesting; leave it unconnected and the mode applies every run.

The single output, also named int, is a plain INT. Wire it into anything that eats an integer - a KSampler's seed, a batch/save counter in a node whose filename template accepts numbers, or a second node of its own kind. The frontend extension then pushes the new value back into the widget after each run, so what you see on screen matches what the graph used.

Installing it

Either route works; there's no heavy lifting either way:

cd ComfyUI/custom_nodes
git clone https://github.com/Lumiyumi/LumyINTP.git

then restart ComfyUI. Or skip the terminal - open ComfyUI Manager, search "LumyINTP", and hit install. There's no requirements.txt and no models folder, which is the whole appeal: this pack cannot participate in dependency hell, and that alone is worth something in an ecosystem where most workflows fail on missing nodes.

Where the wheels come off

The author's own caveat, straight from the release thread: the frontend extension doesn't work with ComfyUI's Nodes 2.0 frontend rewrite. The backend math still runs fine - you'll just lose the live widget update, and the number on screen can drift from reality until you poke it. The standing community workaround is to leave Nodes 2.0 switched off (it broke a lot of utility packs, rgthree included), so if you're on 2.0, expect this cosmetic issue.

Two more behavior notes. First, random_seed rolls every active execution - leave the signal permanently active and you get no reproducibility, which is the opposite of the "lock the seed, change one variable" discipline the community hammers on for debugging. Second, this is a single-maintainer utility pack updated sparingly; it works, but it's a gadget, not infrastructure. For that one specific job - a run counter that knows when to pause - it's exactly right.