Int Switch

The Binary INT Switch (displayed as "Int Switch") is the most straightforward node in the AegisFlow Utility pack: a single Input int that selects between two other ints. Set it to 1 and you get int1 out. Set it to 2 and you get int2. That's the whole job, and sometimes the whole job is exactly what you need.

Why you'd reach for it

ComfyUI has plenty of reroute and switch tools, but this one is about controlled switching. The two value inputs - int1 and int2 - are optional and wired in from elsewhere, which means you can drive them from any INT source in your graph: a batch index, a loop counter, a seed node's output. Then the Input widget is your manual override. Two classic uses:

• A/B settings. Two different CFG values, two different step counts, two different batch sizes - wire both in, flip the widget, compare runs without editing anything.
• Programmatic selection. When your workflow is iterating over options, let another node set Input and the switch becomes a value router that other nodes can control.

The inputs have forceInput set, which just means they're treated as true graph inputs rather than inline widgets - you're meant to wire values in, not type them.

The surprise output

Every node in this pack carries a bit of the author's personality, and here it's the second output: discord, a STRING that is, yes, a hardcoded Discord invite link to the author's server. It's a real output you can wire to a text display if you want, but it's not something to build your workflow around. Take it as a free lesson that this pack is a one-person project with opinions.

Installing it

Standard for the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/aegis72/aegisflow_utility_nodes

Restart ComfyUI, or grab "AegisFlow Utility Nodes" from ComfyUI Manager. No models, no dependencies beyond what ComfyUI ships.

Where people get burned

Don't overthink it - the traps are small. If you leave int1 or int2 unwired and then select that option, the output is None where an INT is expected, which some downstream nodes will reject. And note the widget is genuinely binary: Input is clamped to 1 or 2, so there's no "off" or "pass through" state - one of the two values is always selected. If you need more than two options, this isn't the node; but for a quick two-way value flip, it's about as simple as it gets.