RedNode Router Control

RedNode Router Control is the meta-node for the Router system: a switchboard that counts every RedNode Router in your workflow, de-duplicates their branch colour combinations, and activates one exact combination at a time. It has no inputs and no outputs, because it doesn't move data - it drives the other Routers by telling them which colour state is active. If RedNode Router is the per-branch valve, this is the single knob that controls the whole plumbing.

Here's the problem it solves. Say you have three Routers with a handful of branches each. The colour combinations across them overlap - branch A on Router 1 wants the same colours as branch B on Router 2 - so managing them means remembering which combination lights up which route. Router Control does that remembering for you: it reads every Router's branch colour rules, collapses them into the unique combinations that actually exist, and lets you click one. One non-stacking switchboard, one click, all Routers agree.

How it works

The node scans the workflow for Routers (it finds them the same wireless way the pack's Stage View finds Stage Taps - no wiring, it just knows). For each Router it reads the rules each branch declares, then builds the de-duplicated set of colour combinations across all of them. Activating one combination on the switchboard flips the palette's active colours to match, and every Router re-evaluates against that state. Because it's "non-stacking", selecting a new combination replaces the old one instead of accumulating colours on top of it - so you can't accidentally leave two conflicting routes live at once.

It's the control-room view of the Router system, and it's the thing that makes a many-branch workflow feel like a program with modes rather than a pile of switches.

The honest notes

There are no inputs or outputs to wire, which means there's also nothing to connect wrong - you just place it and drive it. Two practical things to know:

• The de-duplication means the switchboard shows unique combinations, not every branch in every Router. If two branches happen to want identical colour sets, they'll share one switch position; that's intentional, since they'd fire together anyway.
• It depends on Routers actually existing in the workflow. Drop it into a graph with no Routers and there's nothing to switch - the panel just shows an empty count.

Installing it

git clone https://github.com/RedNodeAI/ComfyUI-RedNodeStudio.git ComfyUI/custom_nodes/ComfyUI-RedNodeStudio

Restart ComfyUI, or search RedNode Studio in ComfyUI Manager. No pip deps, no models. Python 3.10+.

Where to start

If you're new to the Router system, add one Router and its palette first and get the colour-driven routing working by hand - the palette's role becomes obvious when you flip a colour and watch a branch swap. Add Router Control once you have two or more Routers and the combinations are starting to overlap in your head. It's the kind of node that looks pointless on a small graph and becomes the whole control surface on a big one.