easy blocker

easy blocker is a gate. It passes a value through only when its continue input is true; when continue is false, it blocks - the value doesn't get through and the branch downstream of it doesn't run. It's the node you use to make part of a workflow conditional: wire a boolean into continue and you've built an on/off valve for everything past it.

This is one half of Easy-Use's little logic toolkit, and it's most useful for gating expensive optional work. Got a heavy upscale pass or a second sampler you only sometimes want? Put a blocker in front of it, drive continue from an easy boolean toggle or a computed condition, and that branch stays dark until the condition says go.

How it works

The node takes a value on in and a flag on continue. If continue is true, in flows out on out and execution proceeds normally. If it's false, the node blocks the path - nothing meaningful comes out and the nodes that depend on this output don't execute. Because ComfyUI only runs a node once its inputs arrive, cutting off the value at the blocker effectively prunes that whole downstream branch for this run.

The inputs and output

• continue - the boolean gate, defaulting to false. True lets the value pass; false blocks it. Wire this from an easy boolean, or from the continue output of easy promptAwait, or any node that computes a true/false condition.
• in - the value to gate. Wildcard type, so it can be an image, latent, pipe, string - whatever you're conditionally passing along.
• Output: out - the value, when the gate is open.

How to install it

Via ComfyUI Manager: search "ComfyUI Easy Use", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

Then install.bat / pip install -r requirements.txt, restart. Preinstalled on comfy.icu.

Common issues

The default is false, which means a freshly-dropped blocker blocks by default. That's the right safe default, but it also means if you wire one in and forget to set or drive continue, that branch silently won't run - and "silently" is the annoying part, because a blocked branch doesn't error, it just produces nothing. If a downstream step mysteriously stops happening after you added a blocker, check whether continue is actually receiving a true value.

The flip side is the good pattern: easy blocker plus easy boolean is the clean way to keep an optional heavy stage in your graph without running it every time. And it composes with the interactive nodes nicely - easy promptAwait outputs a continue boolean specifically so you can pipe your "yes, proceed" decision from a manual checkpoint straight into a blocker. Just remember it gates the branch it sits on, not the entire workflow; independent branches keep running regardless.