view_bridge_Text

view_bridge_Text is the ShowText pattern done right: it displays a string right on the node so you can read it mid-graph, and then passes it through so your pipeline keeps running. ComfyUI's built-in Show Text is a terminal - once you wire a prompt into it for inspection, that's the end of that branch. This node shows you the text and hands it onward. Small difference, huge for debugging.

Because prompt problems are the most common kind of problem. A negative prompt that silently concatenated two strings, a LoRA trigger word that got mangled by a text node, a dynamic prompt that expanded to the wrong thing - the fastest way to catch these is to look at the actual string at the point where it matters, and this node lets you do that without dismantling the graph. You can drop a view_bridge_Text at the input of your CLIP text encode, check the string, and leave it in place forever without it changing the output.

How it works

The text input is what gets shown on the node face and passed through the text output. The display input is a second, multiline text field you can use as a scratch area or a note - type into it and it renders too. Whatever arrives on text is what leaves on text, untouched. There's no parsing, no escaping, no surprises.

The inputs and outputs that matter

• text (STRING) - the value to display and forward.
• display (STRING, multiline) - an editable text area; useful for notes, or for typing a value you want to compare against the live input.
• text (output, STRING) - the same value that came in, so the wire continues.

That's the whole surface. You can't misconfigure it, which is the point of a good debug node.

How to install it

Part of the ComfyUI-Apt_Preset pack - one install, all the view_* nodes come with it. Via ComfyUI Manager search "ComfyUI-Apt_Preset", or:

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

then run install.bat (Windows) or pip install -r requirements.txt, and restart ComfyUI. No model files required.

Common issues & troubleshooting

If you're not seeing text update, it's usually one of two things. The node only renders what arrived on the last run - hit "Run" (or queue) after changing upstream text nodes, don't just stare at it. And because ComfyUI caches upstream results, if the source node didn't change, the displayed text won't either; that's caching, not a stuck node.

Pack-level note, same as every node in this pack: it's a niche pack by a Bilibili-based author with a translated README. The one recurring real-world failure is an IMPORT FAILED for the whole pack when the dependency step is skipped - run install.bat, restart ComfyUI, and confirm the PreView nodes show up before you start debugging text flow.