2🐕Free input box

You've probably hit this before: some downstream node wants an INT, another wants a FLOAT, and a third wants the same value as a STRING for a filename or a text concat - and now you're placing three separate primitive nodes just to feed one number into three places. Free input box collapses that into one field. Type a value once, get it back out three ways at the same time.

How it works

It's a single multiline text box. Whatever you type gets parsed and pushed out as an integer, a float, and a raw string, in parallel - no logic beyond that, no conditionals, no formatting options. The whole point is that all three outputs stay in sync automatically, because they all read from the one field you're actually looking at, instead of you keeping three separate primitive widgets lined up by hand.

The inputs and outputs that matter

• number1 (STRING, multiline, default empty) - the one thing you type.

Three outputs come out of it:

• result_int (INT)
• result_float (FLOAT)
• result_str (STRING)

Wire whichever one your downstream node actually wants - width into result_int, a strength or denoise value into result_float, a filename fragment into result_str - and change the source value in exactly one place from then on.

How to install it

Search Comfyui-ergouzi-Nodes in ComfyUI Manager, or clone it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/11dogzi/Comfyui-ergouzi-Nodes.git

Restart ComfyUI. No models, no extra Python dependencies - it's a plain custom node, same as the rest of this pack. One general note that applies here too: the README marks this English repo as frozen, with further development happening on a Chinese-named sibling pack instead.

Common issues & troubleshooting

Numeric outputs misbehave on non-numeric text. The node exists to give you a number in three shapes - feed it something that isn't actually a number ("a batch of cats", say) and only result_str is going to give you what you expect. If you're wiring up all three outputs, keep what you type numeric; if you only need result_str, free text is fine and the other two outputs simply aren't relevant to what you're doing.

Don't use it as a general-purpose text box for prompts. It's built around double-duty as a number, not as a prompt field - if you just want a multiline string for a caption or a prompt, a dedicated text node keeps the intent clearer for anyone reading the graph later, even if this one would technically also work via result_str.

The real reason to reach for this one: it's less about any single output and more about keeping three values from drifting apart. Change the number once, and everything downstream that reads it - a width, a strength, a label - moves together instead of you hunting down three separate widgets after a spec change.