Stringify Text Input

Let's not pretend. Stringify Text Input is a node whose entire source code is return (text,). You type text in, it hands the same text back. It is the most transparent node in the lazniak/scene_gen pack, and possibly the most redundant-looking thing you'll install this month.

So why does it exist? ComfyUI's type system is stricter than it looks. A multiline text widget is technically a STRING, but ComfyUI treats "widget text" and "wired-in string" as different enough that some nodes refuse to accept a direct text field where they'll happily accept a string connection. This node's job is to be that wire: it takes whatever you typed (multiline, so prose is fine) and emits it as a proper STRING output that flows into nodes expecting a string input.

The actual reason you might want it

There's one behavior worth knowing about, and it's why this node exists inside an AI-video pack: dynamicPrompts is disabled on it. Normal ComfyUI text widgets parse dynamic-prompt syntax - {red|blue|green} randomly picks a variant, [a|b] alternates on each step. Most of the time that's a feature. But when you're feeding a literal string into something like the prompt_instruction of Scene Gen, or passing along a JSON blob, the last thing you want is ComfyUI rewriting your text with bracket magic you didn't ask for.

A plain Text Multiline node would treat {sunset|night} as an instruction to randomize. This node passes it through untouched, byte for byte. That's the whole trick.

It's also handy for a quieter reason: when you've got a string output from another node (say one of Scene Gen's S1–S11 JSON audit strings) and you want to eyeball it as a widget value or hand it to a node that wants a literal text field, running it through Stringify converts a connection back into an editable text box.

How to use it

• Add it from the Scene Gen menu.
• Type (or paste) text into the text field.
• Wire the single STRING output wherever you need a string.

That's genuinely it. There are no other inputs, no settings, no outputs besides the one string. If you don't have a dynamic-prompts collision or a widget-to-connection mismatch, you can skip this node entirely and never miss it.

Honest verdict

It's a one-liner utility, the kind every pack ships and nobody celebrates. It exists because the pack's main nodes take long text instructions, and the author wanted a guaranteed-clean way to feed them without ComfyUI's wildcard parser munging the input. If you run into a "could not convert input" or text that unexpectedly changes between runs, this is a legitimate fix - keep it in your back pocket. Otherwise, it's not a bug if you never touch it.