Nodes/ComfyUI_AIMZ/AIMZ Selective Group Bypasser
ComfyUI Node

AIMZ Selective Group Bypasser

A bypass dashboard for only the groups you actually care about

By AIMZ-GFX·Created 28 days ago·Updated 17 days ago· 3
AIMZ Selective Group Bypasser
  • opt_connection
  • opt_connection

Big ComfyUI workflows live in groups - a region of the canvas labeled "Face upscale," another labeled "First pass," another for "Audio." When you want to run without one of those regions, you bypass it, and if you're using rgthree's Fast Groups Bypasser you get a dashboard listing every group in the graph. That's great until your graph has 30 groups and you only ever toggle three. AIMZ Selective Group Bypasser inverts the idea: you curate a short list of the groups you actually touch, and it gives you one slim row of LED toggles for exactly those.

The result is a compact, one-line node with little status dots - ● ACTIVE / ○ BYPASS - and a ghost delete button per entry. It's the same bypass machinery, minus the wall of checkboxes.

How it works

This one is frontend magic with a placeholder backend. The backend node (AIMZ_SelectiveGroupBypasser) does literally nothing except pass its optional opt_connection through untouched - it's marked as an output node so it shows up in the graph and can anchor a wire. The real work happens in JavaScript, in the pack's web/selective_group_bypasser.js, which ComfyUI loads from the pack's WEB_DIRECTORY.

The JS walks app.graph._groups to find every group title on the canvas, gives you a dropdown, and an "add" button to move a chosen group into your managed list. Each managed group is stored in the node's properties (managedGroups), which is why your list survives saving and reloading the workflow. Toggling an entry flips it between mode 0 (Always) and mode 4 (Bypass) for every node inside that group's bounding box - same thing the right-click "bypass group" does, but from one tidy control.

The optional opt_connection in/out is just a passthrough so you can slot the node into a wire and have it travel with your graph. It does nothing to the data.

The input and output

There's one optional input, opt_connection (any type), and one output, opt_connection, identical. Everything you actually interact with - the group dropdown, add button, and per-group toggles - is on the node's body, not in sockets.

Installing it

Part of the ComfyUI_AIMZ pack. In ComfyUI Manager → Custom Nodes Manager, search comfyui_aimz, Install, restart. Or clone:

cd ComfyUI/custom_nodes
git clone https://github.com/AIMZ-GFX/ComfyUI_AIMZ.git

One thing that trips people: because the UI lives in JavaScript, a stale browser tab may not show the widgets after you install. Hard-refresh (Ctrl+Shift+R) after restarting ComfyUI, and make sure your browser isn't caching the old extension bundle.

Gotchas worth knowing

  • Groups are matched by title. The dropdown shows current canvas groups, but your managed list stores the title string. Rename a group after adding it and the toggle silently stops finding it. Keep names stable, or re-add after renaming.
  • No groups on the canvas → dead node. The dropdown shows "(No Groups Found)" and you can't add anything. This node is only useful in workflows that actually use groups.
  • Frontend widgets and ComfyUI updates. Custom JS widgets are the most fragile thing in the ecosystem - rgthree's own bypass dashboard broke under ComfyUI's Nodes 2.0 frontend rewrite, and third-party widgets are always the first to misbehave after a big frontend update. If the LED row renders wrong after an update, that's the frontend, not your workflow.

It's a quality-of-life node, not a generation one - but for a large, group-heavy workflow it turns "scroll through 30 groups" into "flip two dots."

CategoryAIMZ/Workflow

Inputs (1)

NameTypeDefaultDescription
opt_connectionopt*Optional flow-through connection

Outputs (1)

NameTypeDescription
opt_connection*