Enable / Disable

This one is exactly what it sounds like: a switch. It hands out a single value that says either enabled or disabled, and other nodes in the Searge SDXL workflow read that value to decide whether to do their job or sit out this run. That's the whole node. No sampling, no models, no math.

Worth knowing what it belongs to before you go looking for a use for it on its own. SeargeSDXL is Searge's all-in-one SDXL setup for ComfyUI - one of the very first comprehensive SDXL workflows the community got, back in mid-2023 when everyone was still figuring out how base-plus-refiner was supposed to wire together. It isn't a grab-bag of general-purpose nodes you cherry-pick from. It's the machinery behind one big provided workflow, and nodes like this exist to make that workflow's toggles behave. This particular node lives under Searge/_deprecated_/Inputs, which is the tell: it's a v2/v3-era building block, kept around because the pack stays backward-compatible with old workflows, not something you'd reach for in a fresh graph.

How it works

There's really only one moving part. You pick a state from a dropdown, and the node emits it as a typed signal - a little flag that travels down a wire to whatever downstream node is built to consume it. Think of it as a labelled light switch you can route into several places at once, so one toggle controls a whole section of the pipeline instead of you hunting down and muting individual nodes.

Because the output is a Searge-specific type rather than a plain boolean, it only plugs into sockets that expect it. That's by design - it keeps the workflow's own control logic tidy - but it also means this node is only useful inside a Searge graph that knows what to do with the flag.

The inputs and outputs that matter

There's exactly one input and one output, so this is short:

• state - an enum, either enabled (the default) or disabled. That's your switch.
• state (output) - the same choice, emitted as the ENABLE_STATE type, ready to feed a node that gates behaviour on it.

No seed, no strength, no hidden knobs. If you were expecting parameters, that's not what this is.

How to install it

Grab the whole pack - you can't install one node à la carte.

Easiest path is ComfyUI Manager: open it, search for SeargeSDXL (or "Searge-SDXL"), install, restart.

Manual install is a two-step, and step one trips people up: the pack needs OpenCV, so run python -m pip install opencv-python in ComfyUI's Python environment first. Then cd ComfyUI/custom_nodes && git clone https://github.com/SeargeDP/SeargeSDXL.git and restart ComfyUI. On Windows portable there's a dedicated installer script that handles this and offers to pull the model files too.

Speaking of models: the full Searge workflow expects a pile of them - SDXL base (~7 GB) and refiner (~6 GB) checkpoints, the fp16-fix VAE, a few ESRGAN upscalers, and ControlNet annotators. This enabler node itself needs none of that, but the workflow it lives in does.

Common issues

The main confusion here isn't a bug, it's expectations. People land on this node expecting a general ComfyUI "bypass" toggle and find a Searge-internal flag that won't connect to anything outside the pack - that's the type system doing its job, not a fault. If the socket won't take it, you're trying to plug it somewhere that doesn't speak ENABLE_STATE.

The other one: it's under _deprecated_ for a reason. If you're building something new, use the current v4.x workflow and its UI nodes rather than stitching these older enablers together by hand. They're maintained for compatibility, not because they're the recommended way to work now.