Int (Improved)
Int (Improved) — a seed/steps/count number that actually propagates
- trigger
- value
- json
- trigger
AugmentWaitInt - "Int (Improved)" in the menu - is the trigger-aware passthrough for whole numbers in Augment's Flow Control family. It's for the integers your workflow actually lives on: seed, step count, batch size, frame count, the "which iteration is this" counter. A plain integer primitive is static and compile-time; change it and ComfyUI's cache frequently decides nothing downstream really needs to re-run. This node makes the change stick.
It's also the natural partner to Augment's variable nodes - set a number once, mutate it via increment/decrement, and let an Int (Improved) carry the current value through a staged pipeline in order.
How it works
The honest mechanic, from the source: it doesn't wait or block. execute passes the integer straight through and emits a trigger token. The sequencing comes from the pack's executor patch - on import, Augment rewrites ComfyUI's execution internals so any node that takes or emits a TRIGGER type always re-runs and is never skipped by the output cache. Wire trigger outputs into the next stage's trigger input and you've pinned execution order. The "Improved" part isn't a smarter number; it's a number that provably propagates.
The inputs and outputs
Like the Float, Bool and String Wait nodes, this one has both a widget and an override input:
value(INT, required, default 0) - the widget. Type your seed, steps, count.input(INT, optional) - connect this and it overrides the widget. Great when the integer comes from another node (a variable read, a JSON-extracted value) instead of a human typing it in.trigger(optional) - the sequencing input from a previous stage.- Outputs
value(INT),json(AUGMENT_JSON),trigger(TRIGGER) - the int passes through, the trigger continues the chain, andjsoncarries a structured dump (type and value as a string) for Augment's JSON Extract / JSON Viewer.
How to install
Augment isn't on the ComfyUI registry yet, so it's a manual clone - and the folder name is the one thing that reliably bites:
cd ComfyUI/custom_nodes
git clone https://github.com/augment-lib/augment-ComfyUI augment
cd augment
pip install -r requirements.txt
The clone target must be augment. The pack imports everything as custom_nodes.augment.py.*, so the default folder name augment-ComfyUI makes the nodes silently fail to load. Restart ComfyUI afterward; nodes appear under Augment.
Dependencies: opencv-python, numpy, torch, Pillow, requests - already present from running ComfyUI. No model files, no API key (only the pack's vector nodes need the paid Augment API).
Common issues
- "I changed the steps/seed and got the same result" - the cache. The value only re-propagates when it's wired through this node and the trigger chain reaches your sampler. A bare integer widget with no trigger chain behaves like the stock primitive.
- Node missing after install - folder name. Rename to
augment, restart. - Everything downstream re-runs now - that's the design. Trigger nodes always re-execute, so keep them on the paths where deterministic re-runs actually matter.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| value | INT | 0 | — |
| triggeropt | TRIGGER | — | |
| inputopt | INT | — |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| value | INT | — |
| json | AUGMENT_JSON | — |
| trigger | TRIGGER | — |