Mute / Bypass Repeater

If you've ever wanted to disable a cluster of nodes without deleting them - the upscaler branch, the second sampler, a whole LoRA chain - you know the tedious way is to right-click each node and pick Bypass, one at a time. Mute / Bypass Repeater collapses that into a single control: you wire the nodes you want controlled into its inputs, and when you change its mode, every node connected to it follows.

It's a deliberate reimplementation of the same idea rgthree popularized (its name is lifted straight from rgthree's Mute/Bypass Repeater), rewritten by this pack's author against ComfyUI's newer V3 API and the Vue/Nodes 2.0 frontend - which, as the ecosystem docs record, is exactly the rewrite that broke the original rgthree group-mute rendering. If you're on Nodes 2.0 and your old rgthree muters look wrong, this is the modern replacement that actually renders.

How it works

Place the node, wire the targets into its inputs (the direction matters - nodes you want controlled feed into the Repeater), then right-click the Repeater to cycle its mode between Active / Mute / Bypass. Its mode propagates to every connected input node. That's the whole mechanic, and it's the "connected inputs" model - deliberately different from the Mode Relay, which works by canvas group overlap and can chain onward. The Repeater's oc output is optional, described as a connection point to a Fast Muter/Bypasser for chaining; the Relay is the node the docs point you to when you want cascading group control. For "these specific nodes, one switch," the Repeater is the simpler fit.

Like the rest of the family (Mode Bridge, Relay, Node Collector), it's a virtual node - the Python side returns None, and all mode propagation happens in the frontend JavaScript. No data flows through it, ever.

The inputs that matter

There are no widgets to configure and no data inputs - the input sockets themselves are the interface. Connect the nodes you want controlled, and don't expect to wire anything out of it for data purposes; the oc output exists purely for chaining to other mode-control nodes.

Install

Part of ComfyUI_Eclipse (r-vage). ComfyUI Manager, search ComfyUI_Eclipse, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart ComfyUI - frontend-driven mode nodes need the restart before the JS registers; reloading the workflow isn't enough. No models, no heavy dependencies. And if a shared workflow with [Eclipse] nodes won't load, the pack's v4.0 removed legacy node IDs after the RvTools_v2 rename - run the Workflow Migration Tool.

Common issues

The classic mistake is wiring backwards: if nothing follows the Repeater's mode, the nodes you want silenced probably aren't connected to its inputs. Second most common: expecting it to work across a canvas group - that's the Relay's job, not this node's. And because it only controls mute/bypass state, not values, a "why isn't my data changing?" moment is usually someone reaching for the wrong tool. The Repeater answers one question - "which nodes turn off with this switch?" - and it answers it well.