RedNode Group Rules

Read this node's README entry before you build a workflow around it, because the author is refreshingly honest: Group Rules is marked as a prototype, unfinished, and the node itself carries that label. It's also one of the more interesting ideas in the pack, so it's worth knowing what it's trying to do even while it's still finding its feet.

The idea is a contract system between groups. Instead of you remembering that the face detailer needs the base pass, or that the upscale branch and the detail branch shouldn't both be on, you declare the rules and let the node check them: "B requires A", "A excludes B", "C follows A", "B only if the Paint tab is on". When you queue, the node evaluates those rules against your current group states and shows a panel of which groups will run and which won't - before the run starts. That's the genuinely useful part: the panel is a dry run of your pipeline's execution, so you catch the "I bypassed the group the detailer depends on" mistake at zero cost instead of after a ninety-second queue.

The mechanics are where the prototype edges show. Rules are expressed through a config JSON widget edited by the panel's UI, and the membership question is settled in a smarter way than the rest of the pack: by name, not by which rectangle a node happens to sit in. That's a real improvement over standard ComfyUI group membership and it's the kind of correctness detail that suggests the idea is worth maturing. But this is still an output node whose job is mostly evaluation and display, so treat it as a diagnostic - it tells you what will run, it doesn't enforce anything by itself.

Where you'd actually reach for this: complex workflows with a lot of optional branches where the failure mode is "I queued the wrong combination again." If you've ever stared at a finished queue and realized the upscale ran on the draft branch, you're the target user. For a simpler graph, the overhead isn't worth it - Group Control and Group Modes cover the switching, and the rules are a safety layer on top.

And because it's a prototype, the practical advice is the boring kind: keep an eye on the changelog, don't build a workflow where the whole thing stops working if this node is removed, and don't be surprised by rough edges. The pack's source and README both flag the unfinished state, which is more than most half-finished nodes do.

Installation is the pack:

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

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