Nodes/SAX Bridge/SAX Toggle Manager
ComfyUI Node

SAX Toggle Manager

Scene switching for your whole workflow — SAX Toggle Manager

By so16tm·Created 7 months ago·Updated 10 days ago· 1
SAX Toggle Manager
      ◄config_json{"managed":[],"scenes":{"Default":{}},"currentScene":"Default"}►

      SAX Toggle Manager is the node that makes the whole SAX_Bridge pitch make sense: "Build advanced workflows with fewer nodes. Smart trial-and-error with management nodes." It's a control node that batch-toggles the bypass state and widget values of groups, subgraphs, nodes, and boolean widgets - and saves those states as scenes you flip between with ◀▶ buttons. Pre-register "with/without LoRA," "with/without upscaling," "cache on/off," and switch the entire workflow configuration in one click instead of hunting through the canvas.

      The key detail that sets it apart from rgthree's Fast Groups Bypasser: scenes. rgthree's tool is a dashboard for muting groups; this one layers named scene snapshots on top, so the same toggles can hold several saved configurations and you jump between them. The README's own example is a quick-preview scene (KSampler + grayscale) vs. a full-output scene (upscaler + detailer + save).

      How it works

      It manages the state through a config_json field that the frontend JS owns - you never edit JSON by hand; the node's UI shows you the scene list, the managed items, and the toggle rows. Each scene independently stores the ON/OFF state of every managed item. Switch scene, and the frontend applies all the bypasses and boolean values instantly. The item types it can manage:

      • Group - bypass every node inside a group at once
      • Subgraph - bypass a subgraph node
      • Node - bypass an individual node
      • Boolean widget - flip a specific boolean value on some node

      The selling point is that this needs no wiring and no execution. The node has no inputs beyond config_json, no outputs, and its execute is essentially a no-op - the toggling happens in the frontend and is reflected immediately, with no queue addition. It's declared an output node only so it sits visibly in your graph.

      There's also navigation polish: click a toggle row's label to pan the canvas to that item, and a Back button (keyboard shortcut M by default) jumps you back to the manager from wherever you wandered.

      When you'd use it

      Any comparison workflow where you rerun the same graph in different configurations. Instead of bypassing five nodes by hand, or keeping two full workflow copies, register the switches and toggle scenes. Pair it with a SAX Pipe Collector downstream and you get routing that reacts to the same scenes.

      Installing it

      It's part of the SAX_Bridge pack. ComfyUI Manager → "Install via Git URL" → https://github.com/so16tm/SAX_Bridge, or:

      cd ComfyUI/custom_nodes
      git clone https://github.com/so16tm/SAX_Bridge
      

      Restart, and it's under SAX/Bridge/Utility. No dependencies.

      Gotchas

      Because the switching is frontend-driven, the state lives in the workflow JSON - that's fine for sharing, but it means the node's scenes are your bookkeeping, not a re-execution of anything. If a scene doesn't seem to take effect, the usual cause is that the target nodes changed since you registered them (renamed or deleted groups). And one honest caveat: the same "one click to change a dozen things" power that makes it great also makes it easy to forget which scene you left active - the node shows you, but the canvas might not.

      CategorySAX/Bridge/Utility

      Inputs (1)

      NameTypeDefaultDescription
      config_jsonSTRING{"managed":[],"scenes":{"Default":{}},"currentScene":"Default"}シーン設定データ(JSON)。JS が管理するため直接編集不要。

      Outputs (0)

      No outputs