Group Muter (Multi)

Group Muter is the aggressive sibling of the Group Bypasser. Same idea - pick groups on the canvas, flip a switch, control everything inside them - but where bypass lets data flow through a dead node, mute slams the door. Execution stops at the muted group. That sounds like a downside until you realize it's the whole feature.

Bypass vs mute, applied to groups

Bypassing a group means its nodes are skipped but the graph continues - useful for turning off a branch you'll want back, like an optional upscale. Muting a group means execution halts there entirely. So Group Muter is what you want when a section is in the way: a post-processing pass you don't want to run at all this session, a refinement loop that's eating compute, an experimental stage you're cutting from the run completely. Muting it stops the workflow dead rather than letting it limp past - and that's often the more honest signal that the branch is off.

What it does

AUNSetMuteStateGroup shows you the groups in your graph and lets you select multiple. Toggle, and every node inside the selected groups gets muted - instantly, on the canvas, without running the queue. The node's description calls it out: it provides a UI with toggles for each group in the graph.

Inputs

One input: group_titles, selected via the node's UI (the tooltip is "Select multiple groups using the UI."). No outputs - it's a controller that sits on the canvas and routes nothing.

How it works

Same architecture as the Group Bypasser: the Python class is a thin compatibility stub, and the actual behavior lives in the frontend (web/AUN_set_mute_state_group.js), sharing a group watcher with its bypass twin. The watcher keeps the group list in sync as you edit the graph; when you toggle, it finds every node within the selected groups' bounds and flips its mode to muted or active. Instant, visual, no queue needed.

Because both group nodes share that watcher, they coexist cleanly - you can have one group you bypass and another you mute in the same workflow, controlled from two small nodes.

When it's the right tool

The classic setup is a workflow with an optional quality pass - face fix, refiner, tiled upscale - that you sometimes want and sometimes don't. Draw a group around it, add Group Muter, and you've got a clean "run it / cut it" switch that visibly tells you the state. It also shines for debugging: mute a suspect section and the run stops there, which is exactly where you want to look.

The spatial caveat applies as it does for the bypass version: group membership is geometric, so a node straddling two groups belongs to both. Keep group boundaries clean and you'll never notice.

Installing

It ships in the AUN ComfyUI Nodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/loz2754/AUN-ComfyUI-Nodes

Then restart ComfyUI, or install through ComfyUI Manager (search "AUN"). It's pure UI logic plus a stub - no models, no heavy dependencies beyond the pack's standard requirements, which Manager installs or you can add manually with pip install -r custom_nodes/AUN-ComfyUI-Nodes/requirements.txt.

If you're choosing between the group bypasser and the group muter, the rule of thumb is simple: bypass to silence, mute to stop. For most "I don't want this section running today" cases, muting is the one that actually halts the waste.