Mute Bypass by ID — Triple

Most optional stages in a ComfyUI workflow aren't one node - they're a small cluster. A ControlNet is the loader plus the apply node. An upscale pass is a chain of three. A detailer is a whole subgraph. Toggling those one node at a time is exactly the chore that makes you give up and leave everything running. RemoteControlMulti - "Mute Bypass by ID - Triple" - is the single-node version of the pack's basic RemoteControl, except it can act on three targets at once from one switch.

That's the whole reason it exists. You pick three nodes (or the same optional stage split across three nodes), and flipping one node_status toggle mutes or bypasses all of them together. If your "maybe I'll skip this" is a group of three nodes, this is the cleaner version of right-clicking them one by one.

How it works

Same machinery as its little brother: the Python class is a no-op (do_nothing returns nothing), and all the work happens in the frontend JavaScript. Each of the three target_node_* fields becomes a searchable picker - click one, search by node ID or name, and you get a list that includes nodes nested in subgraphs, with the path shown so you can tell apart nodes that share a duplicate ID in different subgraphs. On every frame the JS resolves all three pickers and sets each target's ComfyUI mode: running (mode 0), muted (mode 2), or bypassed (mode 4) - the same states as the right-click menu.

The one thing to keep straight: all three targets share the same fate. There's no per-target checkbox. One toggle, three nodes, same treatment.

The inputs that matter

Four fields, and only two of them are worth touching:

• target_node_1 / target_node_2 / target_node_3 - the three pickers. Pick whichever nodes make up the stage you want to switch off.
• node_status - the master toggle. On (default) = all three run normally. Off = all three get muted or bypassed.
• mode_select - mute vs bypass, applied to all three at once.

On mute vs bypass, same rule as the rest of the pack: mute skips the node and produces no output (which can break downstream nodes that need it), while bypass skips it but passes the upstream data straight through so the graph keeps flowing. Bypass is the safe default for "quick test without this stage," and it's what's selected by default. There are no outputs - this is a control node, not part of the data flow, so there's nothing to wire.

Installing it

This is one of five nodes in pixelpainter's mute-bypass by node ID pack, so installing the pack gives you all of them. No models, no dependencies. Either search ComfyUI Manager for "mute-bypass by node ID", or:

cd ComfyUI/custom_nodes
git clone https://github.com/pixelpainter/comfyui-mute-bypass-by-ID

Then restart ComfyUI - the picker UI lives in the frontend JS, so it won't appear until the web extension actually loads.

Gotchas

• All three targets move together. If you need to mute two nodes but bypass the third, this isn't the node - the pack's A/B switch or a second Triple handles mixed cases better.
• Search by ID and see a duplicate? Check the path in the picker and pick the entry inside the subgraph you meant. V2.0.0+ of the pack resolves subgraph ID + node ID together so this works reliably - just make sure you're updated.
• Don't expect wires. No outputs is by design, and it's what lets you scatter several of these around a big graph without breaking anything.

If your workflow has a "stage" that's exactly three nodes, this is the one switch you'll actually use. If it's more than three, the Stacker node in the same pack is where you end up.