Display boolean

Boolean values are invisible in a ComfyUI graph. A wire carrying true or false looks identical to one carrying anything else, and if you're debugging a conditional workflow - "why did this branch run?" - the answer is usually "because some boolean somewhere was set the way it was." LF_DisplayBoolean makes that boolean visible: it's a display node that takes a boolean, shows it on the node body, and passes it through on the boolean output.

That's the entire job, and it's a good job. It's the boolean sibling of the pack's LF_DisplayFloat and LF_DisplayJSON - a family of "show me what's actually on this wire" nodes. When you're tracing why a LF_SwitchString picked on_false, or whether that randomization you set up in LF_Boolean actually landed on the value you thought, dropping a display node at the fork is the fastest way to see the truth instead of guessing.

How to use it

Wire any boolean source into boolean - a LF_Boolean node, a comparison result, a value pulled out of an LLM's JSON with LF_GetValueFromJSON - and the node renders the value (the KUL_CODE widget) right on the canvas. It's an output node, so ComfyUI treats it as a terminal point of a branch: that's fine, because your workflow shouldn't route through it. Put it on a parallel tap so the real data flow continues to wherever it was going, and you keep both the function and the observability.

It passes the boolean through untouched, so you can also use it as an intentional waypoint if you like - the output is identical to the input, which makes it a no-op filter that happens to print its payload.

What it's not

It doesn't convert the boolean to a string, it doesn't log to a file, and it won't annotate your prompt. It's strictly an on-node readout. If you need the value turned into text for a filename or a display in the final image, you're looking for a string-conversion node, not this.

Installing it

Part of the LF Nodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/lucafoscili/comfyui-lf

or ComfyUI Manager → LF Nodes → install → restart. No dependencies, no models. The pack is the frozen legacy repo (development moved to lf-nodes), so this node is exactly as shipped - stable, simple, done.

Where people get burned

• Forgetting it's an output node and routing the whole workflow through it. It works (it passes the value through), but you're adding a hop that exists only for display. Tap it off the side instead.
• Expecting a string output. It gives you boolean, not "true". If you need text, convert elsewhere.
• It only shows the value after a run. Until the workflow executes, the node body is blank - don't mistake "nothing rendered yet" for a broken connection.

For the "why did that branch run" moments, this tiny node earns its place in a debug kit.