Show Text Bridge [LP]

Once a workflow has loops or conditional branches in it, an always-on display node becomes a cost you're paying on every pass whether you need it or not. Show Text Bridge is built specifically for that situation: it shows you a string exactly like a normal display node, but only if its output is actually wired to something downstream. No connection out, no execution.

What it does

Feed it text and, if the output is connected to something else in the graph, it displays the value and passes it along. Leave the output dangling - which is a completely normal thing to do while you're still sketching out a workflow - and the node skips itself entirely rather than forcing an unnecessary display step on a run where nobody's consuming the result. That's the whole point of calling it a "bridge": it sits between two things and only does work when it's actually bridging something, which matters most inside loops and conditional branches where a given path isn't always the one that fires.

This is the deliberate opposite of Show Text, this pack's other display node, which runs every time regardless of what's connected. Use Show Text when you always want the check; use this one when the display step itself should be conditional on the rest of the graph.

Inputs and outputs that matter

• text (required) - the string to display. As with Show Text, there's no widget default here, which means it's meant to be wired in from upstream rather than typed by hand.

Output: STRING, list-typed - same as its sibling, so a batch or a loop feeding multiple strings through at once comes out intact rather than collapsed to one value.

Installing it

Through ComfyUI Manager, search "ComfyUI Level Pixel" or "ComfyUI-LevelPixel." Or:

cd ComfyUI/custom_nodes
git clone https://github.com/LevelPixel/ComfyUI-LevelPixel.git

Restart ComfyUI. No dependencies of its own.

Where people get burned

This is the one that confuses people every time, and it's worth saying plainly: if you leave the output unwired while you're actively building and testing a workflow, you will not see anything on this node - that's the intended behavior, not a broken node. If you want to eyeball a value right now while you're still designing, either wire something temporary to the output, or just drop a plain Show Text node at that spot instead and swap it for the Bridge version once the workflow's loop/condition structure is actually settled and you need the conditional-skip behavior for real. Debugging a graph with a node that's silent by design is a frustrating way to lose ten minutes if you don't already know that's how it's supposed to work.