Text 🆎

Text 🆎 is a multiline text box on its own STRING wire, and it exists for the moment when the same prompt needs to reach several places at once. A positive prompt feeding a main CLIP encoder and a ControlNet encode. A caption you want sitting next to the nodes that reference it. A prompt that three branches of the same graph all consume. Without this, you're retyping it into each encoder's widget, and the first time you edit one but forget the other you've got a silent drift between branches.

It's part of the Utility group the pack added in 1.2.0, and the pack's own changelog frames the family honestly: these are the nodes for the gaps that used to mean installing a whole grab-bag pack just to get a text box. ComfyUI core does ship a multiline primitive, so this is a convenience, not a reason to install the pack by itself. But it's a nicely typed one - no wildcard guessing about what's inside, just a STRING that comes out exactly as typed.

How it works

A single multiline text widget (default empty) and one text output that passes the string through byte-for-byte. Nothing gets trimmed, nothing gets interpreted - if you type a newline, the newline travels. Wire it into any STRING input and the value you see in the box is the value downstream gets.

The trick that makes it powerful is "Convert widget to input": right-click a prompt box on a CLIP Text Encode, convert it to a socket, and wire this node in. Do that for every encoder that needs the same text and you've turned five boxes into one.

Install

ComfyUI Manager is the easy route: search for ComfyUI-AusBoss under Custom Nodes and hit Install, then restart. Or manually:

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

Restart ComfyUI and Text 🆎 sits under 🆎 AusBoss/Utility. No extra Python dependencies - the pack uses only what ComfyUI already ships. Minimum ComfyUI 0.27.1 (Manager enforces this at install), and hard-refresh with Ctrl+Shift+R after frontend updates.

Common issues

The output really is exactly what you typed - so if you pipe a multiline prompt into something that expects single-line (like a filename token or a node that joins lines with commas), you'll get line breaks in an awkward spot. That's a feature for CLIP encoders and a footgun elsewhere; trim at the consumer. Also note this is a plain source node, not an output node - if you want to see the string that's flowing through mid-graph, that's the pack's Show Text 🆎, which passes the same value through while rendering it on the node face.