Fast Groups Bypasser

The bigger a workflow gets, the more time you spend right-clicking, selecting a group, and hitting Set Group Nodes to Never. Fast Groups Bypasser turns that into a list of toggles sitting in one corner of the canvas.

What it is

A dashboard. One toggle per group, on = the group's nodes are active, off = bypassed. It covers the groups of the graph the node sits in and the groups inside every subgraph - including switching a subgraph node itself, which takes its contents with it. Right-click the node for Bypass all, Enable all and Toggle all.

rgthree popularized this shape and it's genuinely used - Fast Groups Bypasser shows up in 48 threads in the KB's corpus, behind only that pack's Power Lora Loader. Same idea here, with the pack's own sort and filter options.

How it works

Nothing executes. The node has no inputs and no outputs at all - it's not a socket you wire, it's a control surface. The Python class exists so the node is registered and appears in the prompt; the executor never runs it.

All the behaviour lives in web/js/fast_groups_bypasser.js, which keeps its list in sync with the graph on a half-second tick - so groups you create, rename, delete, or mute by hand show up without you touching the node.

The properties (right click → Properties Panel) are worth three minutes:

• sort - position (canvas order), alphanumeric, or custom alphabet.
• customSortAlphabet - letters, or comma-separated prefixes, that define the custom alphabet order. Number your groups 01_model, 02_control, 03_upscale and pick this.
• matchColors - comma-separated group colours, names like red or hex, so only matching groups are listed.
• matchTitle - a regex, same filtering job.
• showAllGraphs - off means only the groups of the graph on screen; on lists everything, filtered by the two options above.
• toggleRestriction - default, max one (switching one on switches the rest off), or always one (same, plus the last active group can't be switched off). This is your A/B harness: two model groups, always one, and you can never end up with both.

In practice

Group by stage, not by node type. A refine group, a upscale group, a face pass group - things you want to switch off as a unit while you're iterating. Colour them, then use matchColors on two bypassers if the workflow gets long enough that you want one panel for generation and another for post.

Installing it

ComfyUI Manager → search ComfyUI-BCNodes → install → restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/0xBeycan/ComfyUI-BCNodes
pip install -r ComfyUI-BCNodes/requirements.txt

Restart and hard-refresh the browser tab, since the node is entirely frontend code. If you have the pack's old ComfyUI-AutoBypass folder lying around, delete it - same author, older name, and duplicated nodes.

Common issues

Bypass is not mute, and it can break a workflow. Bypass tries to route the link through the node; when there's no matching pass-through, the node is effectively skipped and the downstream input is simply gone. A required input then fails with Required input is missing - this is such a standard ComfyUI injury that the same pack ships an Auto Bypass node specifically to dodge it. Mute is the blunter, safer option when you just want a branch to stop existing.

It does nothing in API / serverless mode. Bypass is a frontend concept. Export a prompt after your toggles are set and the prompt reflects that state forever; a prompt assembled without the frontend can't be switched by this node at all.

There is a second node with this name. rgthree's Fast Groups Bypasser is in the wild and broke badly under ComfyUI's Nodes 2.0 frontend rewrite - its author confirmed the rendering problems and said he wouldn't be porting it. This is an independent implementation, so if the one you're using is misbehaving, the other is worth a try. Note ComfyUI registers it as BC_FastGroupsBypasser, so both can be installed side by side without conflict.