Group Bypass Child
The marker that makes group-bypass cascades chain
- from_parent
- to_children
HYBS_GroupBypasser_Child (display name "Group Bypass Child") is the middle link in the pack's group-bypass cascade. The Parent marks the source of a cascade, Children are the targets, and this node's job is to chain them - a Parent toggled from the Group Bypasser panel drags its Children along, and a Child can feed another Child for multi-level chains.
Standing alone it's nearly featureless, and that's by design: it's a marker node, not a processor. The frontend reads the wire topology to know which groups travel together, and the backend just passes its input through untouched. If you're building a workflow where a whole cluster of groups should bypass in unison - refinement passes, style stages, a multi-step pipeline you frequently turn off as a unit - this is the node that holds the chain together.
How it works
The schema sums it up: "Frontend-controlled cascade target marker. Backend passes through its input."
- from_parent (
ANY) - a UI-only link from a Group Bypass Parent or another Child - to_children (
ANY) - a UI-only link to the next Group Bypass Child
Because from_parent is typed ANY, the links don't carry real data - the backend's execute returns whatever it received, but in practice nothing of substance travels these wires. They exist so the frontend extension can see the connections and build the cascade graph. Each Child sits inside a group; when the panel toggles the parent group's bypass, every group holding a linked Child flips too.
Wiring it
For a chain of three groups:
- Group Bypass Parent
to_children→ this node'sfrom_parent(in the second group) - This node's
to_children→ another Child'sfrom_parent(in the third group) - Repeat for as many levels as you need - the schema explicitly supports "Parent or another Child" as input sources.
Everything stays inside the pack's group-bypass system; nothing here affects regular node execution outside of it.
Installation
Standard pack install:
cd path/to/ComfyUI/custom_nodes
git clone https://github.com/hybskgks28275/ComfyUI-hybs-nodes.git
pip install -r ComfyUI-hybs-nodes/requirements.txt
Or "ComfyUI-hybs-nodes" via ComfyUI Manager, then restart.
Honest take: you only need this node if you need the cascade. A single group toggle doesn't require it - the Group Bypasser panel handles that on its own. Reach for Parent/Child the moment you want one switch to control several related groups, and not a moment before. And as with the whole trio, it's a browser-side feature: make sure the panel renders in your frontend before building anything on it.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| from_parent | ANY | UI-only link from a Group Bypass Parent or another Child. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| to_children | ANY | UI-only link to the next Group Bypass Child. |