AutoMute

AutoMute calls itself "workflow autopilot," and the description is more honest than most. It watches certain nodes on your canvas and, based on whether they're present and active, automatically mutes or unmutes other groups and nodes. You set it up once, and from then on the graph reorganizes itself around which branch is actually doing something. No manual mute-clicking between variants, no "oh no I forgot to re-enable the refiner" moments.

Before you use it, understand the trick - because it's a bigger one than the name suggests. The Python side of AutoMute is a no-op. Look at the class and you'll find RETURN_TYPES = (), no inputs, no outputs, and a noop function that returns nothing. All the actual logic lives in the JavaScript frontend extension that ships with the pack (web/auto_mute.js), which registers the node's real behavior in the browser. That means AutoMute never touches your data and never runs during a queue - it's a workflow-organization node, in the same family as rgthree's Fast Groups Muter, existing purely to keep a big graph workable. Same category of tool, different engine: where rgthree gives you a dashboard you toggle by hand, AutoMute tries to decide for you.

What you actually do with it: add the node to a canvas, open its settings (there's a "⚙️ AutoMute Settings" modal in the frontend), and tell it which nodes to monitor - by title, with options like case sensitivity, exact-match vs partial, and whether to only count connected nodes. Then define the target groups and the rule: mute them while a monitored node is active, unmute when it isn't, or the reverse. The frontend scans the graph, matches node titles against your patterns, and flips the mute state of the targets accordingly, keeping the canvas dirty flag updated so you can see what changed.

Because it's frontend-only, the practical implications are worth stating plainly:

• It works while you're editing in the browser, not during an API-run batch. Nothing in the backend state changes.
• It's a pure graph-management convenience. No performance cost, but also no guarantees about edge cases - the matching is title-based, so rename a node and the rule silently stops firing until you update the pattern.

Installing it

Same one-pack install as every ComfyPanel node:

cd ComfyUI/custom_nodes
git clone https://github.com/Ginolazy/ComfyPanel
# restart ComfyUI

Or ComfyUI Manager → search "ComfyPanel". No models, no heavy deps. If the AutoMute settings modal doesn't show up, the usual suspects are a stale frontend cache or ComfyUI not fully restarting after install - hard-refresh the browser tab.

Where AutoMute shines is a workflow with mutually exclusive variants: an upscale branch and a face-detail branch, a refiner and a straight-to-latent path. If you're tired of babysitting which one is muted, this is a genuinely handy autopilot. If your graph is small enough to read at a glance, it's an extra node that mostly entertains you. Install it for the day your workflow outgrows your attention span.