FETextInput

Yes, this is a node whose entire job is "give you back the text you typed." FETextInput is a multiline text field with a string output - a pass-through, nothing more. Type a prompt, a filename prefix, a tag list, whatever; it comes out the other end as a STRING you can wire anywhere a string is accepted.

It sounds almost too dumb to exist. But it solves a real ergonomic gap: plenty of nodes in this ecosystem expose their text as an input widget that's not easy to wire around - and more importantly, once a text value needs to be consumed by two different places, you want a single source of truth. One FETextInput feeding two downstream nodes beats typing the same prompt into two widgets and letting them drift apart. It's the string equivalent of a reroute: not smart, just convenient.

Input and output

• input - a multiline STRING widget, default empty.
• Output: output, the exact string, untouched.

That's the whole schema. No options, no transforms, no wildcard parsing, no trimming.

How it compares

The ecosystem has a thousand of these (Everywhere, RGThree's text nodes, WAS Suite's text inputs - all do the same thing), and you almost certainly already have several installed. FETextInput isn't doing anything the others don't. Its actual role is as part of a family: in the fexli pack it pairs with FETextCombine (join strings), FETextCombine2Any (stringify anything), and FERandomPrompt (random string) to form a mini text toolkit. If you're already using those, this one completes the set without pulling in another pack.

Install

From fexli-util-node-comfyui:

cd ComfyUI/custom_nodes
git clone https://github.com/fexli/fexli-util-node-comfyui
cd fexli-util-node-comfyui
pip install -r requirements.txt

Or ComfyUI Manager → search fexli-util-node-comfyui → install → restart. No config.yaml, no dependencies beyond the pack's standard two.

Honest verdict: you don't need to install a pack for this node, and if you already have a text-input utility, don't bother switching. But if you're in the fexli pack anyway and your graph needs a shared, editable text source that multiple nodes read from, it's a zero-config, zero-surprise addition - the node you add last and forget about immediately.