TT_TextInput

This is the most boring node in a small pack, and that's exactly what makes it useful. TT_TextInput is a multi-line text box whose output is the text you typed. That's the whole job. It doesn't transform, merge, or randomize anything - it just hands a string to whatever you wire it into.

So why does it exist? The pack is built around prompt generation, and TT_TextInput is the feed line. The flagship TT_StoryCombiner has nine text fields built into it, but the author's own workflow keeps that text in separate TT_TextInput nodes instead. That way the words live in one visible, labeled place, can be shared across several combiner boxes or other nodes, and stay editable without hunting through inline strings buried in a graph. It's the editorial layer: TT_TextInput holds the copy, TT_StoryCombiner does the rolling.

How it works. The process function returns its input untouched. There is no mechanism to describe, which is the entire selling point - a passthrough with no side effects, no hidden parsing, no surprises.

The one input that matters: text, a multi-line field. The output is a STRING, which you wire into any string input that accepts a connection - a TT_StoryCombiner box, a CLIP Text Encode's prompt field, or another text-handling node.

Where it fits. Pair it with the rest of this pack: TT_TextInput is the hand-written text source, TT_TextFileSelectorNode is the file-based source, and both output the same type, so you can swap them in and out of the same wires. Typical flow: three TT_TextInput nodes holding settings, a story, and a style line → wired into TT_StoryCombiner → one combined prompt out.

Install and gotchas. Installing the pack once gets you all four nodes - ComfyUI Manager, search "TT_TextTools," install, restart; or git clone https://github.com/zzubnik/TT_TextTools into ComfyUI/custom_nodes. No dependencies, no models, nothing to download. Troubleshooting is almost insultingly easy: if you get an empty string, you typed nothing, and if nothing comes out of the node you forgot the wire. The honest caveat is that core ComfyUI already puts a multi-line field on most text nodes, so this earns its keep specifically when you're building the multi-source prompt setups this pack is for - for a one-off text field, you probably already have one.