Group Bypasser 🎯

One node that mutes every group in your graph

You know the moment: the workflow is working, you just need to skip the refiner pass, kill that ControlNet section, or turn off the upscaler for a quick test - and the only way you know is right-clicking twenty nodes one at a time and picking bypass. That's the exact pain Group Bypasser 🎯 exists for. Drop one node on the canvas and it adds a toggle for every group in your workflow. Flip a toggle and every node inside that group goes into bypass mode. There's also a "⏭️ Bypass All Groups" button for the "run this without any of the expensive bits" case.

The name undersells it a little: the node doesn't bypass a node - it manages bypass for the whole graph. It's from KreonXV, a hobbyist dev who quietly ships small utility nodes (a ComfyUI-Whiteboard lives in the same family). Single-purpose and frontend-only: no API, no key, no model downloads, zero Python dependencies.

Be honest with yourself about whether you need it, though. The heavyweight answer to this exact problem is rgthree's Fast Groups Bypasser, a filterable dashboard that does the same job and a dozen others. If you already run rgthree-comfy - and if you build large workflows you probably should - you don't need this node. If you don't want a whole utility pack just to mute a couple of groups, this is the leaner option.

How it works

The Python side is a shell. GroupBypasserNode barely does anything; the real logic lives in web/group_bypasser.js, which runs in your browser. When the node is created it scans every group on the canvas, sorts them top-to-bottom, and attaches a toggle widget to itself for each group. Flip one, and the JS finds every node whose center falls inside that group's bounding box and sets its mode to 4 (bypass) or 0 (always-on) - the same modes you get from right-clicking a single node and choosing bypass, applied to a whole group at once.

Two details are worth knowing. First, the node auto-refreshes its toggles, checking about once a second, so adding, renaming, or moving a group updates the widget list without restarting. Second, bypass mode (4) is not mute mode (2): bypass keeps the connections and skips execution, so downstream nodes still see something on the wire. That's usually what you want for testing.

The inputs and outputs

The data ports are a formality. There's one optional input, trigger, and one output, trigger, both of type * - they pass a value straight through. You can ignore them entirely, or wire any token through the node if you want it sitting in your graph's path. The real controls are the toggles and buttons on the node's face. Because the node is flagged as an output node, some workflows treat it as a graph endpoint; harmless, just don't be surprised when it shows up as "final."

Installing it

The README's instructions are dead simple: copy the folder into ComfyUI/custom_nodes and restart. The clone version is the same thing in one line:

cd ComfyUI/custom_nodes
git clone https://github.com/kreonxv/ComfyUI-GroupBypasser

Restart ComfyUI and search "Group Bypasser" in the node menu. There's no requirements.txt, no pip step, no model to download - the whole pack is one Python file and one JS file. ComfyUI Manager may already have it indexed; if not, the clone above is all there is.

Where people get burned

Three real gotchas, all grounded in how the code actually works.

A node you expected to bypass didn't. Detection is geometric: only nodes whose center lands inside the group's bounding box get toggled. A node that pokes halfway out of the group gets skipped. Drag it fully inside and the toggle will catch it.

The toggles don't show up at all. This is a browser-side JS extension, and that's a fragile place to live. ComfyUI's Nodes 2.0 frontend rewrite broke a pile of JS-heavy utility packs in late 2025 - rgthree's fast muters were the famous casualty. If your widget row is missing, you're probably on the new canvas; switch back to the legacy canvas and reload.

You're installing a fresh repo from an unknown author. Custom nodes execute arbitrary code on your machine, and there's no vetting process - the LLMVISION malware incident is the cautionary tale. This one is as low-risk as a node gets: MIT-licensed, a pass-through class, and no dependencies beyond what ComfyUI already ships. Still, take the two seconds to eyeball the repo before you clone. That's good hygiene for every node, not just this one.