PD Show Text

The string just went through three concatenation nodes and you have no idea what it actually looks like. That's the moment you want PD Show Text: wire any string into it and it displays the value right in the node, on the canvas, where you can read it without squinting at the console. It's the pack's answer to "how do I see what's on this wire," and for a node whose whole job is to be boring, it's remarkably handy.

ComfyUI core has a version of this concept now, but most packs still ship their own - and this one has one behavior worth knowing: it's an output node that also passes the string back out as a list, so you can drop it in the middle of a graph as a tap, not just a dead end. Read the value, keep the wire going.

How it works

The mechanism is a nice little trick. The node's notify function grabs the current node's ID from ComfyUI's hidden inputs, finds the node in the workflow's serialized graph, and writes the incoming text into its own widget values. So the display you see isn't a separate preview overlay - it's the node literally updating its own text box with whatever arrived. That's why it works whether the text is typed or comes from a string-processing pipeline: it always shows the resolved value of the wire.

Because it's an output node (OUTPUT_NODE = True), it always runs, which also makes it a handy "make sure this branch executes" anchor when a silent cache is skipping work you wanted to inspect.

The input and output

• text (STRING) - the string to display. It's forced as an input socket, so you'll normally wire it from upstream rather than typing.
• Output: STRING (list) - the same text passed through, so you can chain display into another node.

Installing it

Part of Comfyui_PDuse by 7BEII. ComfyUI Manager (search "PDuse") or:

cd ComfyUI/custom_nodes
git clone https://github.com/7BEII/Comfyui_PDuse.git
cd Comfyui_PDuse
pip install -r requirements.txt

Restart ComfyUI. It's pure UI plumbing - no models, no heavy deps beyond the pack's standard set (numpy, Pillow, scipy, opencv-python, torchvision). Docs are Chinese-first.

Where people get burned

Not much to burn on - that's the point. The one caveat: the passthrough output is a list (the node declares OUTPUT_IS_LIST), so if you wire its output into a plain string consumer you might hit a list-vs-string type mismatch; use it as a display tap and keep your real string flowing on a parallel path. And if you type text directly into the widget, remember the display logic still runs - it's a read-back, not a typed value that stays put.