ImpactControlBridgeFix

Somewhere in the Flux Continuum workflow, a chain of nodes needs to be switched on and off based on the task you've selected - inpainting vs. txt2img vs. upscaling - and you don't want to right-click a dozen nodes to do it. ImpactControlBridgeFix is the pack's take on Impact Pack's Control Bridge: a control node that sits in the wire and, when you flip it, stops the current execution or tells the node on its output to go active, muted, or bypassed. The "Fix" in the name is real - the pack ships a web/impactpackfix.js to make this behave with the Impact Pack bridge protocol.

How it works

The node has two meaningful controls: mode (Active or Stop/Mute/Bypass) and behavior (Stop, Mute, or Bypass).

• behavior = Stop: with mode active, the input value passes straight through. With mode off, it returns an ExecutionBlocker, which halts the workflow at this node - nothing downstream runs.
• behavior = Mute or Bypass: the node inspects the workflow graph (via the embedded workflow JSON ComfyUI sends to custom nodes), finds the nodes connected to its output, checks their current state, and tells them to flip to active/mute/bypass accordingly. It then sends a sync message to the frontend and interrupts processing so the state change takes effect.

It's a conditional execution switch, and the mechanism it uses - comfy_execution.graph.ExecutionBlocker for Stop, PromptServer.send_sync + nodes.interrupt_processing() for Mute/Bypass - is exactly how Impact Pack's own bridge works. If your ComfyUI is too old for the execution model, the node prints a warning and Stop degrades.

Inputs and outputs

• value - any type (*). The data to pass through.
• mode - BOOLEAN, default true. Labeled "Active" vs "Stop/Mute/Bypass".
• behavior - dropdown: Stop, Mute, Bypass.

Outputs one value (any type), and the node is marked OUTPUT_NODE. In the Flux+ workflow it's used to gate whole module chains, letting the Output selector activate only the branch for the current task.

Installing it

Ships in robertvoy/ComfyUI-Flux-Continuum:

cd ComfyUI/custom_nodes
git clone https://github.com/robertvoy/ComfyUI-Flux-Continuum

or ComfyUI Manager ("Flux Continuum"), restart. It wants the Impact Pack bridge protocol to talk to, so keep Impact Pack installed - the pack's README lists it as a dependency for a reason.

Where people get burned

The Mute/Bypass modes depend on reading the embedded workflow metadata (extra_pnginfo). If you're running the node via the API without a full workflow payload, there's no graph to inspect and the state-flipping silently does nothing - the node just passes the value through. Also, "Stop" halts the whole workflow at this point, which is dramatic; if the intent was to skip one branch, Mute/Bypass is gentler. And because it mutates node state, expect it to feel like a button, not a parameter - flip it, and the graph rewires itself in ways that persist.