text

Some nodes exist to be impressive. This one exists to be a text box. ttN text is a single multiline STRING input that outputs the same string - nothing more, nothing less - and it's the kind of node you don't appreciate until you're trying to share a prompt value between two places without copy-pasting it twice.

In ComfyUI, prompt text usually lives inside the CLIP Text Encode or loader node itself. That's fine until the same phrase needs to appear in two prompts, or you want to edit a quality block in one obvious spot. A dedicated text node gives you a single source of truth you can wire anywhere a STRING input exists.

How it works

It's the most transparent node in the pack: text in, text out, byte for byte. It supports dynamic prompts, so if you type __anything__ for a noodlesoup wildcard, it resolves like the in-node prompt boxes do. That's genuinely the only magic here - which is the point. The author's own description is "Basic TextBox Loader," and that's the whole pitch.

Inputs and outputs

• text - multiline STRING. Type whatever you want.
• text - the same STRING, as a wired output.

Wire it into a tinyterra tinyConditioning positive/negative box, a pipeLoader, a textConcat input, or a core CLIP Text Encode if you've converted it to accept input. If you need to display text or print it to the console, the pack's textDebug is the sibling for that.

Installing it

It's part of tinyterraNodes:

cd ComfyUI/custom_nodes
git clone https://github.com/TinyTerra/ComfyUI_tinyterraNodes.git

or install tinyterraNodes via ComfyUI Manager. No dependencies, no model files, restart and go.

Where it fits (and where it doesn't)

The tinyterra text family is a sliding scale of ceremony: this is the bare minimum, textConcat adds joining, textDebug adds a display/console output, 7x TXT Loader Concat is the bulk version for seven strings. If all you need is "a prompt I can wire around," this is the one to reach for - it's the least to think about and it can't do anything surprising.

One honest caveat: if your only goal is a fixed prompt for one sampler, don't add a node for the sake of it. ComfyUI's own prompt boxes do the job. The value shows up the moment a string needs to exist in more than one place - shared quality blocks, wildcard sets, or values you want to drive from a single edit point. That's the use case this quietly wins.