Mode Bridge Get

Mode Bridge Get is the receiving end of this pack's wireless mute/bypass control. You pair it by name with a Mode Bridge Set, and whenever that Set's mode changes - you mute it, bypass it, or bring it back to active - this node echoes the change to every node connected to its inputs. It has no outputs and no data of its own. Its entire job is to be a fan that spreads a mode state across a cluster of nodes that aren't connected to the Set by any wire.

If that sounds like the reverse of what you'd expect (a node with inputs that receives, not outputs that emit), that's the design. The pack's own description is precise: "Subscriber: receives mode changes from the Mode Bridge Set with the same name. Connect nodes to this node's inputs to control their mode." You drag connections into the Get from the nodes you want controlled. In the graph it reads backwards - wires point in, not out - but that's exactly how a listener should look: things feeding it, none of its own output.

How it works

Like its Set counterpart, this is a virtual node - execution returns nothing and the real behavior lives in the frontend JS. The pair works by name: pick the same bridge name on both nodes and they're bound, regardless of where they sit on the canvas, including across subgraphs. The classic pattern is one Set as your "master" and several Gets spread around the workflow, each wired to the local nodes it should silence - so flipping one switch bypasses the face-detailer in the main graph and the upscaler branch tucked inside a subgraph at the same time.

The name is everything. A Get with a ⚠ next to its bridge name is telling you no Set with that name exists - the docs list that as the #1 bridge troubleshooting item. The pairing is string-matching, not a wire, so a renamed node or a mangled paste quietly breaks the link.

The inputs that matter

There are no widgets beyond the bridge-name combo, and there are no output sockets at all - just inputs, which is where you attach the nodes you want to control. A beginner instinct is to look for an output to connect onward; there isn't one, and that's not a bug.

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 nodes like this one genuinely need the restart, not just a workflow reload, before the JS registers. No models, no heavy dependencies. If you grabbed a shared workflow with [Eclipse] nodes that won't load, the pack's v4.0 removed legacy IDs after the RvTools_v2 rename - run the Workflow Migration Tool before tearing your install apart.

Common issues

Get never reacts: name mismatch (check the ⚠), or the connected input nodes aren't the ones the mode applies to - the Get propagates to its input connections, so wire the nodes you want silenced into the Get, not away from it. Green activity dots not updating after muting a group is another documented symptom; it's a frontend refresh quirk, and the fix is the same one the docs point at - make sure the Set and Get share the exact name, then re-run. And remember the boundary: this controls mute/bypass state only, never data values.