[Feature Request] Programmatic Fast Bypasser about rgthree-comfy

[rgthree]

This comes up a lot but, unfortunately, it's not really possible to toggle mute/bypass with an input as they are in two completely different phases of execution.

Muting, Bypassing, and other actions are all modifying the active workflow in the browser in real-time. Whether you use ctl+M, or a Fast Muter, etc. when you do so, it's changing those nodes' status right there in the browser workflow--there's no communication with the server.

When you queue a prompt, ComfyUI takes the current browser workflow, and sends it as-is to the backend, which executes it independently. Things that have been muted/bypassed are stuck as muted/bypassed (I actually think Comfy doesn't even send them to the backend).

Further, an input is a value passed from one node to a connecting node in the backend, during that nodes' execution. At this point, it is infeasible to then mute/bypass a node or group based on the value of an input as we're no longer in the browser to manipulate the workflow that would have been sent to the server. (At least not without an extensive re-write to ComfyUI's execution and APIs.)

[gisu]

Ok, thank you for the explanation. It will probably need lifecycle hooks and only the ComfyUI team can integrate them.