RedNode Palette

RedNode Palette is the switchboard behind the pack's whole color-routing system. The idea: instead of wiring boolean gates everywhere to decide which branch runs, you tag branches with colors and turn colors on and off. Switch a color on and every branch carrying it takes over. No wires, no booleans, no Any Switch fallback chains - just a palette of colors you toggle.

The mechanism, spelled out: this node holds the set of colors and which of them are on. The pack's Router nodes (the advanced switch this pairs with) each pass when their tagged colors are on; a branch whose color is off simply doesn't run, and - the useful part - losing branches never execute, so you're not paying compute for a pipeline you didn't pick. The Palette is the single source of truth for that state, and because it's one node, you can drive it from elsewhere: a Control Panel row, a saved scene, or the pack's Pass node, which flips colors as data flows past it.

The inputs are the familiar panel pattern: a preset dropdown that applies a saved set of colors (with "custom (live)" leaving them as they are), and a config JSON box holding the colors and which are on. The panel above the node edits that JSON for you; hand-editing the config directly is the escape hatch if the UI is unavailable, and it makes the whole routing setup copyable between workflows as plain text.

Why is this better than boolean switches? Three reasons, in order of how often they matter. First, legibility - a graph where routing state lives in one colored panel reads a lot better than a graph studded with toggles and fallback nodes, which is exactly the wire-hiding tension the plumbing layer is always navigating. Second, the state is one thing: swap the palette's active colors and the whole graph re-routes, which is the same benefit Group Modes gives you for groups but applied to execution branches. Third, it composes with the Pass node, so a pipeline can re-route itself as data reaches a stage rather than waiting for you to flip something.

The honest caveat, and it's the standard one for wire-free control: the palette state lives in the browser/frontend, not as data flowing through the graph. It's a great interactive tool for the workflow you're actively running, and it's not how you'd parametrize a headless or shared API workflow, where explicit switches and converted-to-input values are the honest answer. Use color routing for the living workflow; keep wires for the parts that must be unambiguous.

If the whole concept feels abstract, start with one concrete case: a draft/final pair of branches. Color "draft" and "final" on the palette, tag each branch, and toggle which one runs from a single node instead of muting half the graph. You'll feel the win immediately.

Installation is the pack:

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

or search RedNode Studio in ComfyUI Manager, restart. No pip dependencies; works with any model.