Remote Int (on prompt)

The integer counterpart to Remote Boolean (on prompt), and it works the same unusual way: at the start of prompt execution, it reaches into another node by numeric ID and forcibly overwrites one of its widgets - no wire, no visible connection anywhere on the graph. Where the boolean version flips switches, this one sets numbers: a seed, a step count, a resolution, whatever integer widget you point it at.

Why you'd reach for this instead of a normal wire

The obvious way to control a widget from elsewhere in the graph is to right-click it, "Convert widget to input," and wire a value in - visible, debuggable, normal. Remote Int exists for the cases where that's awkward or impossible: automation and loop-driven workflows where you want to programmatically set a value on a node without restructuring the graph around it, or where the target widget was never meant to be an input in the first place. The README is explicit that this class of node is built for that use - forcibly setting widget_value at the start of the prompt.

It's filed under the pack's _for_test Logic category, same as its boolean sibling - a power tool for scripted workflows, not something a normal generation graph needs.

The inputs

• node_id (INT, default 0) - the target node's numeric ID. Find it through ComfyUI-Manager's badge overlay (#ID Nickname) or ComfyUI's own node info.
• widget_name (STRING) - the exact internal name of the widget being overwritten. Not always the same string as the label shown on the node.
• value (INT, default 0) - the number to force onto that widget.

No output - this is a side-effecting node (is_output_node: true), executed for what it does to the target rather than anything it hands downstream.

The same trap as its boolean sibling: IDs move

Node IDs aren't stable across graph edits. Add, remove, or reorder nodes and the ID you pointed this at can start hitting the wrong target - or nothing at all - with zero indication on the graph itself, since there's no wire to go stale visibly. And per the README, a type mismatch between what this node sends and what the target widget actually is gets silently disregarded rather than raising an error. Both failure modes are quiet. Re-verify node_id after editing anything near the node you're remote-controlling, and label the node so its purpose is obvious later.

Installing it

Standard Impact Pack install. Via ComfyUI Manager: search ComfyUI Impact Pack, Install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Impact-Pack
cd ComfyUI-Impact-Pack
pip install -r requirements.txt

(portable: python_embeded\python.exe -m pip install -r requirements.txt), restart. No models needed.

Common issues

Value not landing: check node_id first - it's the most likely culprit if the graph has changed since you set this up - then confirm widget_name matches exactly. If both check out and it's still not working, confirm the target widget is actually the plain widget type you think it is; a widget that's already been converted to an input, or one driven by a different data type, won't accept the forced value and will just be silently ignored rather than telling you why.