HT Unmute All

You've been experimenting: muted a branch here, bypassed a node there, toggled half the graph off to chase a bug. Now you want a clean run with everything active, and the thought of right-clicking twenty nodes to unmute them is exactly the kind of busywork ComfyUI loves to make you do. HT Unmute All is the reset button - run it and every node in the workflow is set back to active. That's the entire job, and it's a genuinely useful one.

What it does

Optional signal_in (a * wildcard, so anything can drive it), optional... that's it. When it executes, it walks the workflow's node list - it reads the workflow graph from extra_pnginfo, which ComfyUI passes to every node - and sends an unmute command for each node ID. The signal_out passes your signal through untouched, so you can hang it on a wire and let its execution be the "unmute everything now" moment in a sequence.

The honest mechanism (and the catch)

Same machinery as its sibling HT Node State Controller: it emits impact-node-mute-state events through PromptServer for every node in the graph. Which means the mute/unmute state it's resetting is the Impact Pack node-state mechanism, and Impact Pack needs to be installed for the frontend to act on those events. If Impact Pack isn't there, the node still runs and still passes your signal through - it just won't actually unmute anything, which is exactly the kind of silent no-op that wastes an afternoon. Install the pack and Impact Pack, then verify by muting one node and watching this reset it.

Also worth knowing: it unmutes everything - it won't bypass anything, it won't restore your previous toggle state, and it won't skip muted-but-intentionally-off nodes. It's a sledgehammer, not a scalpel. If you need surgical control, that's the Node State Controller or rgthree's group muters.

When you'd use it

• The end of a debugging session: flip the workflow back to full strength in one click.
• Batch runs where a prior iteration left things muted: drop this at the start of a pipeline to guarantee a clean slate.
• Recovery after loading someone else's workflow where half the graph arrives muted or bypassed.

Installing

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/ArtHommage/HommageTools.git
cd HommageTools && pip install -r requirements.txt

restart, or Manager → "HommageTools for ComfyUI". No models, no extra Python deps - just remember the Impact Pack dependency above.

The honest take

It's a one-trick node, and the trick is good. As a recovery tool it's worth having in the graph even if you rarely use it - the day you load a workflow where someone muted a dozen nodes is the day it earns its place. Just don't build a workflow around it: the alpha disclaimer applies, and it depends on another pack's event plumbing, which is exactly the kind of integration that breaks when ComfyUI updates its frontend protocol.