Mode Bridge Set

Muting and bypassing nodes is one of the most useful gestures in ComfyUI, and in a big workflow it becomes a chore: you want to switch off the upscaler branch, or bypass the face-detail pass, and you're clicking three nodes that live in three different corners of the graph. Mode Bridge Set is this pack's answer - a wireless control channel for exactly that. You give it a name, and any Mode Bridge Get node with the same name becomes a fan that echoes its mode changes anywhere in the workflow, including inside subgraphs. No wires between them. It's mute/bypass by radio, and it works because both nodes are "virtual" - their behavior is implemented in the pack's frontend JavaScript, not in data flowing through the graph.

The setup is two nodes with a shared name (a combo on each). The Set is the publisher: when its mode changes (right-click → mute or bypass), every Get subscribed to that name flips to match. The Get then propagates that mode to whatever nodes are connected to its inputs. What you end up with is a single master switch that can silently silence a whole cluster - or the entire workflow - without a single wire crossing the canvas.

How it works

The schema is a skeleton: the Set has no data inputs and one oc output typed *, which exists only so you can chain it to a Switcher, Repeater, or another Get if you want. Execution just returns None - nothing travels down the oc wire. The real work happens in the frontend (eclipse-mode-nodes.js), which listens for the mode change and fans it out by name. This is a deliberately different model from rgthree's group muting: instead of grouping by region on the canvas, you group by name, which is why it keeps working when nodes are inside subgraphs or scattered across a huge canvas.

The docs' troubleshooting is worth heeding before you build anything: if a Get shows a ⚠ next to its bridge name, no Set with that name exists in the graph (or the name got mangled on paste). The pairing is purely name-based, so a typo is a silent failure - no error, just a fan that never receives.

The inputs that matter

Honestly, there are none to set on the node itself beyond the bridge name combo - that name is the entire contract. Connect oc only when you want to daisy-chain control into a Switcher or Repeater.

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 - and note that because these nodes are frontend-driven, you need a restart, not just a workflow reload, or the JS won't be loaded. No models, no heavy deps. And if you're loading a shared workflow with [Eclipse] nodes that fails, the pack's v4.0 removed legacy IDs after the RvTools_v2 rename - run the Workflow Migration Tool.

Common issues

A Get that never updates: name mismatch or missing Set - check the ⚠ indicator. The mode synced but only one direction: the docs describe bidirectional sync between a Set and its Gets, so if flipping the Set doesn't move the fans, you're looking at a stale workflow or a Get with an unconnected input. And the biggest conceptual gotcha: this is a UI-control node, so it has no effect on the data your workflow produces - if you expected it to alter a value, that's not what it does. It toggles mute/bypass state. That's it, and that's plenty.