show text

Every text pipeline needs a way to look at what it's producing, and base ComfyUI's answer is weak. Show text is the fix: wire any string into it and the node displays the value on the canvas, in a widget on the node itself, and - the clever part - writes it back into the workflow metadata so it survives a save and reload. It's the single most useful debugging node in this pack, and if you build multi-stage prompt chains, you'll want one at every junction.

The implementation is borrowed from pythongosssss's ComfyUI-Custom-Scripts show_text.py, which is a good pedigree - this is a proven pattern, not a novelty. The output is also list-capable, so it handles multi-string flows, not just single lines.

How it works

The text input is forceInput (you wire it in; there's no typing box), and when the node runs it does two things. First, it renders the text into the node's UI so you can read it on the graph. Second - and this is what most display nodes skip - it finds itself in the workflow's extra_pnginfo and writes the value back into its own widget values. Result: save the workflow, reload it, and the text that was flowing through is still visible on the node. That makes it genuinely useful for diagnosing a pipeline after the fact, not just live.

Inputs and outputs

• text - STRING, forceInput, the value to display
• Output: STRING (list-capable) - the same text, passed through so you can chain it

Yes, it passes the text through. Think of it as a tap on the pipe, not a dead end.

Installing it

# ComfyUI Manager: search "ymc suite" and install ymc-node-suite-comfyui
# or:
cd ComfyUI/custom_nodes
git clone https://github.com/YMC-GitHub/ymc-node-suite-comfyui

Restart after installing. Dependencies are four small pure-Python PyPI helpers that self-install; no models, no GPU footprint.

Gotchas

• It's an output node, so it has to be connected to something downstream of the data you care about to execute. If it shows nothing, check that it's actually reached by the graph - orphaned debug nodes don't run.
• Because it writes back to the workflow JSON, older saved workflows that included one can have a stale value baked in. Not a bug, but if the text on the node disagrees with what you think you typed, re-run the workflow.
• If WAS Node Suite is installed alongside, Manager may flag shared node names between the packs - the WAS suite has its own text display nodes, so you can pick either; just don't rely on both if you see conflicts.