Group Controller

Group Controller is a workflow-control node: it toggles a group of nodes between running, bypassed, or muted. The idea is to switch a whole chunk of your graph on or off - say, turn an upscale group off for a fast test pass, then back on for the real run - without hand-toggling every node inside it.

This is one of aidec's experimental extras, and it's the barest of the bunch. The README documents the queue and loader nodes in detail and flags the rest as test pieces, and Group Controller's info schema is genuinely minimal - a single control mode in, a status out. So set expectations accordingly: it's a rough utility, not a polished group manager, and the well-known rgthree "Fast Groups Muter/Bypasser" nodes do this job with far more surface if that's what you're really after.

How it works

You pick a control mode - bypass or mute - and the node applies that state. Bypass and mute are ComfyUI's two ways of taking nodes out of a run: bypass passes data through as if the node weren't there, mute stops it (and its branch) from executing at all. Group Controller wraps that toggle so it can be flipped as part of your graph rather than only by right-clicking nodes in the editor.

The input that matters

• control_mode - bypass or mute. That's the whole control surface: which of the two "turn it off" modes to apply.

The only output is status. It's an output node, so it can sit in the graph and do its job without feeding anything downstream.

Installing it

cd ComfyUI/custom_nodes && git clone https://github.com/aidec/Comfyui_TextBatch_aidec, then restart ComfyUI (or ComfyUI Manager → Install via Git URL). No models, no heavy dependencies. Category: TextBatch.

Where people get burned

• It's minimal and experimental. With just a mode input and a status output, there's not much configurability exposed here, and the README treats it as a test node. Don't expect the polish or the group-targeting UI of a dedicated tool.
• Bypass vs mute matters. They're not interchangeable. Bypass lets data flow through the disabled nodes (useful mid-chain, so downstream still gets something); mute kills the branch entirely (useful when you want it to genuinely not run). Picking the wrong one is the usual source of "why did my graph behave weirdly" - match the mode to whether downstream still needs data.
• Consider the alternative. If group enable/disable is a real part of your workflow, rgthree-comfy's Fast Groups Muter and Bypasser are the community-standard nodes for it, with proper per-group toggles. Group Controller is fine for a quick switch inside this pack; reach for rgthree when you want to actually manage groups.

Honestly the least essential node in the pack - worth knowing it exists, but if group control is your goal, you have better options.