🍒Prompt_Text / 文本输出

Prompt_Text is the node you add when you want a visible text field sitting in your graph - a place to type (or paste) a prompt, a note, a filename, anything - and have it appear in the workflow's UI and pass through as a string. Every seasoned ComfyUI user has a dozen of these scattered through their graphs; the difference here is that this one is a proper output node, so whatever you type gets rendered into the UI's prompt panel when the graph runs. It's the lazy person's documentation layer: you can see the prompt that produced an image without hunting for the text node that feeds it.

How it works

Nothing clever, and that's the appeal. One multiline text input, one STRING output (labeled 文本) that passes the text through untouched. It's declared OUTPUT_NODE, so it shows its content in the UI, and it handles lists - feed it a list of strings and it'll return the list and display each entry. There's even a progress bar over the list, which is a nice touch for a node this simple.

The one input

• text - multiline STRING, default empty. Type anything; wire the output into a CLIP Text Encode, a Save Image filename prefix, or anywhere a string is expected.

Installation

Ships in ComfyUI_KimNodes:

cd ComfyUI/custom_nodes
git clone https://github.com/wjl0313/ComfyUI_KimNodes

Restart ComfyUI. No dependencies beyond the ComfyUI standard library.

Common issues

Honestly? There's not much to get wrong. The one thing to know is that because it's an output node, it participates in the UI - the text it received on the last run is what shows in the prompt panel, not necessarily what's in the box right now if you're feeding it from upstream. If you're just using it as a notes label and the UI panel clutter bothers you, you can leave it unconnected and it still displays. It's the kind of node you won't think about until you realize your workflow has no visible text anywhere and you can't remember what that branch was for. Then it earns its place.