AGSoft Text Multiline

Sometimes a node is just a text box, and that's the whole point. AGSoft Text Multiline takes a multiline string, passes it through untouched, and hands you the same string on the other side. It exists because ComfyUI's built-in text handling can be finicky about where line breaks are allowed - this gives you a predictable, always-multiline input you can drop anywhere a string is expected, and drive from a wire when you want.

How it works

One input, text, typed STRING with multiline: true - so the field grows as you type, newlines included. The tooltip also notes it supports dynamic prompts (the {wildcard}-style syntax some packs expand at queue time), because the string just passes through and the wildcard machinery downstream doesn't care where the text came from.

The output is the same STRING, unchanged. That's the entire mechanism - and it's the right amount of mechanism. Its job is to be a stable, multiline-capable text carrier in a graph where you want to type a long prompt once and feed it to several places, or swap between typed text and a node-fed string by rewiring one cable.

Why you'd use it instead of a built-in node

Honest framing: it's a convenience, not a breakthrough. But convenience earns its place when:

• You want a big comfortable text field for a long prompt without fighting a one-line widget.
• You need a clean "source of truth" for text that multiple nodes read (a prompt hub - type once, fan out).
• You're building a workflow you'll share, where an explicit labeled multiline box reads better than a bare primitive.

It's the right choice when you want exactly what you typed, verbatim - no concatenation, no cleaning, no delimiter logic. If you find yourself wishing the output were processed, that's what the concatenate, split, or replace nodes in the same pack are for; this one deliberately does nothing but carry text.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/Art-xmaster/comfyui-AGSoft

Restart ComfyUI, or ComfyUI Manager → "comfyui-AGSoft". No models, no dependencies. There are no real failure modes here - the one thing to remember is that pass-through means what you type is what goes out, including trailing newlines and leading spaces. If your prompt seems to have extra blank lines downstream, that's your text, faithfully preserved; trim it in the box.