Nodes/ComfyUI_Eclipse/Fast Mode Toggle Native
ComfyUI Node

Fast Mode Toggle Native

The mute/bypass switchboard that lives inside your subgraph

By r-vage·Created 10 months ago·Updated a day ago· 33
Fast Mode Toggle Native
    • oc

    You've got a workflow with two upscaler branches, or a face detailer you only want half the time, and you're sick of right-clicking nodes to mute or bypass them one at a time. That's the itch this node scratches: wire the nodes you want to control into Fast Mode Toggle Native and each one becomes a checkbox on a single little control panel. Tick it and the target runs. Untick it and it goes into whatever "off" mode you chose - Bypass by default, Mute if you'd rather. One node, five targets, no hunting through a web of wires.

    The niche is an old one - rgthree's Fast Groups Muter and Bypasser built a reputation on exactly this dashboard idea. But this is the "Native" variant, and the difference is the headline: its checkboxes are promotable Boolean controls. Tuck the toggle inside a ComfyUI Subgraph and you can promote those switches up to the subgraph node's inputs, so the branch selection is controllable from the parent graph without opening anything. On top of that it's written for the current era of ComfyUI - the V3 node API and the Nodes 2.0 frontend - which is more than the old guard can claim after the rgthree/Nodes 2.0 mess.

    How it actually works

    Nothing here runs on the backend. Fast Mode Toggle Native is a virtual node: its Python execute() returns nothing, and every behavior lives in the pack's frontend JavaScript (eclipse-mode-nodes.js). That's why the schema is nearly empty and why the node is effectively free - it just manipulates ComfyUI's own node-mode system.

    The schema declares no fixed inputs at all. On the canvas what you get is a row of anonymous * input sockets that auto-grow: drag the output of any node you want to control into one, and a native Boolean checkbox appears on the toggle, labeled with that node's title. Wire in a second node and a second checkbox grows. Each switch tracks its target's real mode, both ways - flip the checkbox and ComfyUI mutes/bypasses the target; mute the target by hand elsewhere and the checkbox follows. Disconnect the wire and the checkbox disappears, so keep connections tidy.

    The one output, oc (type *), exists so you can chain the toggle to sibling mode-control nodes like Fast Mode Switcher or Mute / Bypass Repeater. You don't need it for basic use.

    Right-click the toggle and the options you'll actually touch:

    • Mode: Bypass / Mode: Mute - what "off" means when you untick a box. Bypass routes around the node as if it weren't there; Mute turns it off entirely. Default is Bypass.
    • Restriction: default / max one / always one - make your branch toggles behave like a radio group so only one target is active. This is the A/B/C-branching killer feature.
    • Enable all / Mute all / Toggle all - bulk actions for the whole panel.

    Installing it

    Install the pack once, normally - the toggle is one node among roughly 150 that ComfyUI_Eclipse ships. ComfyUI Manager (search "ComfyUI Eclipse"), or:

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

    No model files, no heavy downloads. requirements.txt is mostly torch, numpy, Pillow, opencv - stuff ComfyUI already ships. Find the node under 🌒 Eclipse → Tools.

    Where people get burned

    • It mutes nodes, not groups. The checkbox controls whichever single node its wire points at. For whole regions you're chaining wires or using the pack's group-aware siblings - this one is per-node.
    • The name vs. its older sibling. Plain "Fast Mode Toggle [Eclipse]" does the same per-node toggling without the subgraph-promotion and title-stability machinery. If you're building reusable subgraphs, use the Native one; if you're just lazily muting a node, either works.
    • Frontend-dependent. Because it's JS, "node shows up but the toggles do nothing" almost always points at a stale frontend: restart ComfyUI and check the server log for import errors first (the README's own advice), then hard-refresh the browser so the freshly shipped eclipse-mode-nodes.js actually loads instead of a cached copy. The pack is tuned for current frontends (classic and Nodes 2.0); on a genuinely old ComfyUI install you'd rather use the older behavior it keeps around.
    • Version churn. Eclipse 4.x removed all legacy node IDs. If you load an old RvTools_v2-era workflow, run the pack's built-in Workflow Migration Tool rather than hand-patching.

    It's a small utility and it knows it. But once you've used a toggle to flip between two upscale paths in three clicks instead of six right-clicks, you'll wonder why core ComfyUI doesn't ship it.

    Category🌒 Eclipse/ Tools

    Inputs (0)

    No inputs

    Outputs (1)

    NameTypeDescription
    oc*Optional connection to other mode nodes.