LayerUtility: Boolean

About as simple as ComfyUI nodes get: you set a toggle, on or off, and it hands that value back to you two ways - as an actual BOOLEAN you can wire into anything that switches behavior, and as a STRING ("true"/"false") for anywhere you need it as text instead of a typed value. No image processing, no model, just a value sitting on a widget that other nodes can read.

It earns a spot in a workflow the moment you start building things that aren't purely linear. Expose it as an API parameter so callers can flip a feature on or off without editing the graph. Feed the string output into a filename or a caption so the render itself records whether some option was active. Or just use it as a manual switch you toggle by hand while testing two versions of a workflow.

How it works

There's nothing to explain mechanically - it holds one widget, bool_value, and passes it out in two forms. The value only changes when you change it (or when it's set via the API), so treat it as a static input, not something computed from anything upstream.

The inputs and outputs that matter

• bool_value (default false) - the toggle. That's the entire input surface.
• boolean output - the raw true/false, for wiring into a switch, gate, or conditional node.
• string output - the same value as text, for captions, filenames, or debug overlays.

How to install it

Ships as part of the ComfyUI Layer Style pack. ComfyUI Manager - search ComfyUI Layer Style (or LayerStyle), install, restart. Manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/chflame163/ComfyUI_LayerStyle
pip install -r ComfyUI_LayerStyle/requirements.txt

then restart. Lives under 😺dzNodes → LayerUtility → Data. Nothing to download - pure logic, no models involved.

Common issues & troubleshooting

There's genuinely very little to break here - it's a widget with two output ports. If it isn't behaving, check the obvious thing first: you're reading the wrong output type where the other one was expected (wiring string into a port that wants a real BOOLEAN, for instance - ComfyUI's type checking should catch that at connection time, but double-check if a link looks refused).

The node isn't in your node list at all. That's the pack failing to import, not this node - LayerStyle pulls in a long dependency chain, and one broken library (transformers paired with a stray TensorFlow install is the recurring offender) takes down every LayerStyle and LayerUtility node at once. This is especially common on an old, pre-split install (the pack used to ship combined with LayerStyle Advance, which carries the heavier dependencies); delete and reinstall clean, or hit "Try Fix" in ComfyUI Manager and read what it actually failed on before assuming this specific node is the problem.