🚀 Text Field

Yes, this is just a text box. You type text, it outputs that text as a STRING. ComfyUI already has a primitive text node, so why does this exist? Because sometimes you want the prompt to be a first-class, wired input - something other nodes can read, that travels with the workflow, and that you can connect multiple things to without hunting for widgets. That's the whole job, and it does it with one unglamorous input and one output.

Honestly, it's a node you'll mostly ignore - until you're building a reusable sub-workflow where the prompt shouldn't be buried inside a node's widget, but should be a visible input that you can rewire per instance. For that, a dedicated text node is the cleaner pattern than a widget you can't easily connect to.

How it works

There is no mechanism to speak of. It has a multiline text input (a widget with a default of empty) and returns that string unchanged as a text output. Whatever you type - a prompt, a negative prompt fragment, a filename, a caption - comes out the other side byte-for-byte. The multiline flag means you can paste in a paragraph and it won't collapse newlines, which is occasionally the difference between working and not when the downstream node cares about formatting.

Inputs and outputs

• text - multiline STRING widget.
• Output: text - STRING.

That's the entire surface area.

Install

ComfyUI Manager (search "YarvixPA") or

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

restart. It's under ComfyUI-YarvixPA/Utils/Text. No dependencies beyond the pack's own.

When it earns its keep

Three situations. Building template workflows where the text should be an obvious, labeled input rather than a widget nested in a node. Feeding text into a custom node that requires a wired STRING input (many of this pack's own nodes and third-party utils want an input, not a widget). And keeping prompts centralized - one text node feeding several conditioning branches means you edit one place instead of several. If none of that applies, ComfyUI's built-in primitive node will do fine and this one is harmless either way. It's the definition of a utility node: nothing clever, but exactly what you need when you need it.