Control Bridge

Muting and bypassing nodes is normally something you do by hand, clicking around the graph. Control Bridge lets the workflow do it to itself while it runs. Connect it to some control nodes and, based on its mode and behavior, it can switch those nodes to active, mute them, or bypass them - pausing the current execution, updating the mute state, and inserting a fresh queue to continue. It's part of Impact Pack's experimental automation kit, the toolset for building workflows that reconfigure themselves across iterations (loops that turn a branch off after the first pass, for instance).

This is power-user territory. It's genuinely useful for automation, and it has sharp edges that the pack documents plainly.

How it works

The node's own description spells out the truth table. When behavior is Stop and mode is active, the input value simply passes straight through to the output - a no-op that lets execution continue. When behavior is Mute/Bypass and mode is active, the connected downstream node is switched to active. When mode is set to Stop/Mute/Bypass instead, the roles invert: with behavior Stop it halts execution of the current node, and with behavior Mute/Bypass it flips the connected node into the Mute or Bypass state. In short: mode says "which situation are we in," behavior says "what to do about it," and the effect lands on whatever control nodes you've wired to the output.

The inputs and outputs that matter

• value (any type, *) - the wire it lives on; the value passes through so you thread it into your graph like a pass-through.
• mode (BOOLEAN, default on) - the active vs. stop/mute/bypass condition selector that picks which half of the truth table applies.
• behavior (Stop / Mute / Bypass) - the action to take: leave things running, mute the target, or bypass it.
• Output: value (*) - the passed-through value, so downstream nodes keep flowing.

How to install it

ComfyUI Manager: search ComfyUI Impact Pack, Install, restart.

Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Impact-Pack
cd ComfyUI-Impact-Pack
pip install -r requirements.txt

Run the pip in ComfyUI's Python environment and restart. No models.

Common issues & troubleshooting

It breaks with batch count above 1. This is the headline limitation, straight from the README: Control Bridge does not function correctly when the batch count exceeds 1. Run these workflows one at a time.

Put it - and everything like it - at the end of the workflow. The pack is explicit: Queue Trigger, Set Widget Value, Set Mute State and similar state-changing actions should execute after the Control Bridge section, at the very end of the graph. If those fire before the Control Bridge, its behavior isn't guaranteed. Structure the workflow so all the reconfiguration happens last.

Randomized seeds interfere. The README notes it won't behave reliably if the seed randomizes before the Control Bridge runs. The recommended pattern is to change the seed with Set Widget Value at the end of the workflow rather than using widget randomization - or at least ensure any randomization happens after the Control Bridge section.

Nothing toggled. Make sure the nodes you intend to control are actually connected to this node's output - the state change lands on connected control nodes, so an unwired target does nothing.