Light-Tool: Input Text

ComfyUI's native prompt boxes are fine until you need a string that isn't a prompt. That's where Light-Tool: InputText lives: it's a multiline text field that outputs the text as a STRING, so you can wire it into a wildcard processor, a filename builder, a JSON helper, or an API call without pretending it's conditioning.

One input, input_text, multiline. One output, text, typed STRING. There's nothing else to configure, and that's the appeal.

The mechanism - and the one surprise. The node passes your text through, then strips leading and trailing whitespace before returning it. For a prompt or a filename that's exactly what you want; you never noticed the accidental trailing space that was quietly breaking your seed loop or your filename template. But if you're building something where whitespace is data - a code fragment, an indented block, a string you're going to hash - this node will mangle it. That's not a bug, it's a design decision that leaks out. For whitespace-sensitive content, a node that doesn't touch your input is the safer choice.

Why you'd bother. The value isn't the text box, it's the output routing. This node turns a UI widget into a wire, which matters in workflows where the same string feeds multiple consumers, or where you want a human to edit a value without digging into a node's widget stack. Pair it with a text display node (the pack's ShowText) if you want the value echoed back visibly.

It's also just convenient. Text handling in ComfyUI is a quiet swamp of String, STRING, multiline flags and converters, and having a node that guarantees a clean STRING out of a box you typed into removes one class of type errors before they happen.

Installing. Same as every node in this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/ihmily/ComfyUI-Light-Tool.git
pip install -r requirements.txt
# restart ComfyUI

Or skip the terminal: ComfyUI Manager → search ComfyUI-Light-Tool → Install → restart. No models, no downloads, nothing heavy - this pack's dependencies are the usual numpy/torch/Pillow/OpenCV stack, and a plain text node touches almost none of them.

Verdict. It's the most boring node in the pack, and it's one you'll keep. Every workflow ends up with a loose string that needs to become a proper typed output, and this is a zero-surprise way to do it - provided you remember the whitespace trimming when you're handling anything where spaces carry meaning.