Bubba View Text

Bubba View Text is the simplest node in the pack, and it solves a problem everyone hits eventually: the value of a string inside your graph is invisible. A prompt builder expanded a wildcard and you want to see the actual final text? A metadata node computed a path and you want to check it? The text is trapped inside a wire. This node displays whatever multiline text it's given - connected or typed in - right on its own body, and passes the text through unchanged.

That "passes through unchanged" part is what separates it from a dead-end display. Because it's an output node that also re-emits its input, you can drop it inline without breaking the data flow: display the string and keep feeding it to whatever needs it next. It's the ComfyUI equivalent of a print() debug statement that doesn't disturb anything.

How it works

There's one input, text (multiline, defaults to empty), and one output, text, which is exactly the same string back out. The tooltip is the whole spec: "Text to display on the node. Supports connected and multiline strings." You can type text in the widget and display it without connecting anything, or wire a string output in and watch it update each run. Because it's an output node in the graph-execution sense (it always runs and downstream caching works backward from it), it's safe to place anywhere - but a display node that must fire every run does cost you the cache behind it, per the node-plumbing docs, so don't scatter a dozen of them through a heavy graph.

The input that matters

Just text. Everything else about this node is the display itself.

How to install it

Same pack as everything in Bubba Nodes. ComfyUI Manager → "Bubba Nodes" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/bubbafett5611/bubba_nodes.git

restart ComfyUI, and pip install -r requirements.txt if the console asks. No models, no downloads, needs ComfyUI v0.27.0+.

Gotchas

Honestly, this is the node you can't break. The only things worth knowing: the display is a frontend feature, so what you see on the node is rendered by the UI, while the backend sees a plain string - if a workflow behaves differently under the API than in the UI, that's unrelated to this node. And if you're debugging a very long string, the on-node text can be dense; grab a wider view by wiring the output to a proper text viewer or the metadata debug node if the pack's display isn't enough. One more small note: it's an output node, so a graph with View Text as a terminal will still execute the branch feeding it - which is usually exactly what you want when you're checking a value. It's a genuinely thin utility, so there's not much more to say; the pack is young and this is one of those quiet nodes that just works.