⚜️ Text Display

Not a headline node - it's plumbing. Connect any STRING output to it, and it shows the text on the node itself while also passing it straight through, so it doesn't dead-end whatever chain it's sitting in. The pack's README doesn't call this one out specifically, but once you're running Wildcard Processor and Style Injector - nodes that quietly rewrite your prompt before it ever reaches CLIP - you end up wanting something like this in nearly every graph.

Why you'd actually reach for it

Wildcards and style injection mean the text you typed and the text that hit the model are two different strings. If an image comes out weird and you can't tell whether it was the wildcard pick, the style injection, or your own prompt, the fastest way to find out is to look at the resolved text directly. Wire SDXL All-In-One's + prompt / - prompt outputs into one of these - or Wildcard Processor's resolved string, or Style Injector's positive/negative - and you can read exactly what got sent downstream.

Inputs and outputs that matter

There's really only one input: text (STRING, required, no default - something upstream has to actually feed it). The output is that same string, unchanged, so you can keep chaining nodes after it without losing anything. It's also marked as an output node, meaning ComfyUI will run and display it even if nothing downstream consumes its output - you can use it as a dead-end inspection point if you just want to check a value without wiring it any further.

Installing it

Via ComfyUI Manager: search Comfyui FOCUS nodes, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/DJ-Tribefull/Comfyui_FOCUS_nodes

Restart ComfyUI. Nothing to configure - it's a display node, no model files, no dependencies beyond the pack itself.

Common issues & troubleshooting

Nothing shows up. The text input has no default, so something upstream needs to already be producing a string. If the box is genuinely blank rather than erroring, check that the string you fed it isn't itself empty - an unresolved wildcard token pointing at a missing .txt file, or a truly empty negative_in field upstream, will both show up here as nothing to display rather than as an error.

You're worried about breaking your graph by adding one mid-chain. You won't - because it passes the string through unchanged, it's safe to drop several of these at different points in a big workflow purely as checkpoints, without affecting what actually reaches your CLIP Text Encode nodes downstream.