Orchestrator Group Bypasser

Once a workflow has an SDXL branch, a Flux branch, and a Pony branch all sitting on the same canvas, right-clicking "bypass" on every single node in the section you don't want gets old fast. Orchestrator Group Bypasser turns that into one toggle per section: drop it on your canvas, and it gives you a switch for every ComfyUI Group (the labeled boxes you draw around clusters of nodes) already in your workflow.

How it works

This node has no data inputs and no outputs - check the schema and it's empty on both sides, because it isn't a data node at all. It's a pure front-end control panel. Under the hood it scans your graph's Groups, builds one toggle widget per Group title, and when you flip one, it walks every node physically inside that Group and sets its mode to either 0 (normal) or 4 (bypass) - ComfyUI's native "skip this node, but try to hand its input straight through to its output where the types line up" behavior.

The one thing to know before you rely on it: the toggles are exclusive. Turning one Group on automatically turns whichever other Group was active back off - it's a radio button, not a bank of independent switches. That's fine if your Groups really are "pick exactly one variant" (SDXL vs Flux vs Pony), but it's not built for freely mixing multiple Groups on and off independently.

The inputs and outputs that matter

There's nothing to wire - that's the design. The two things that actually matter are outside the schema entirely: name your Groups clearly, because the toggle labels come straight from the Group title, and remember that only nodes drawn genuinely inside a Group's box get toggled with it - a node sitting just outside the border is untouched.

How to install it

ComfyUI Manager: search ComfyUI_Custom_Switch, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/tritant/ComfyUI_Custom_Switch

then restart. No requirements.txt, no models, nothing beyond torch (already part of ComfyUI). It's a small, single-author pack - built by tritant, ~16 stars, last touched October 2025 - that does one specific thing rather than a whole framework.

If this sounds familiar, it should: rgthree-comfy's Fast Groups Bypasser is the well-established version of the exact same idea, with a filterable dashboard on top, and if you already run rgthree-comfy you already have that capability. Tritant's version is a lighter, single-purpose take on the same trick for people who don't want to pull in rgthree's whole pack just for group toggling. The exclusive one-at-a-time behavior isn't unique to this node either - it's a known shape in this corner of the ecosystem; people have posted looking for more control than an exclusive "always one" toggle gives them, which tells you it's a real, common limitation of this design pattern, not a bug specific to this pack.

Common issues & troubleshooting

No toggles show up. This node lists Groups, not nodes. If your canvas has no Groups drawn (select some nodes, right-click, Add Group), there's nothing for it to find. An unnamed Group also gives you an unlabeled, useless toggle - title it.

I flipped a toggle and the output downstream barely changed. Bypass isn't the same as fully off - a bypassed node tries to pass its input through to its output where the types match, so something can still flow through an "off" Group. If you need a section to produce genuinely nothing when it's off, that's the sibling Orchestrator Group Muter node, not this one.

It didn't pick up a Group I just added. The toggle list refreshes as it redraws; if it looks stale, nudge the node (move it slightly, or reload the workflow) to force a rescan.

Widgets render oddly or won't open. This node works by patching the canvas directly - dynamically adding widgets and redrawing itself, the same technique rgthree's Fast Groups Bypasser uses. That style of node is exactly what broke under ComfyUI's Nodes 2.0 (Vue) frontend rewrite for rgthree. There's no reported issue against this specific pack, but if you're on Nodes 2.0 and something looks broken here, switching back to the legacy canvas is the known fix for the same class of problem elsewhere.