StringMultiline (for Interactive)

Same idea as InteractiveString, but the text box actually gives you room to write. InteractiveStringMultiline is for the case where the string you're holding is a full prompt, a block of negative-prompt text, or anything longer than a short tag - the single-line version would just be awkward to edit for that.

It's part of the pack's literal-node trio (string, integer, float) that the author frames as built for interactive workflows specifically - values meant to sit cleanly in a graph that pauses and waits on InteractiveSelector/InteractiveSwitch clicks rather than running straight through.

How it works

Type or paste text into the multiline widget; it comes out unchanged as a STRING every time the node executes. Nothing fancy - no formatting, no templating, no transformation. The whole value proposition is just "a text box that fits more than one line," feeding whatever downstream node expects a string.

Common placement: as the parameter_string input on an InteractiveSelectorWithParameters node, when the thing that differs between branches is a full prompt rather than a short label - pick a branch, get its full prompt text back out of the matching InteractiveSwitchWithParameters.

The inputs and outputs that matter

• string (required, STRING, default "", multiline) - the text itself. The multiline flag is the only real difference from InteractiveString's widget.
• string (output, STRING) - wire it wherever text is expected: a parameter_string, a CLIPTextEncode, anywhere.

That's the entire node - one field that happens to be roomier than its sibling's.

How to install it

Bundled with the full pack. Via ComfyUI Manager: search "ComfyUI-Interactive" and install. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/lquesada/ComfyUI-Interactive

Restart ComfyUI. No requirements.txt, no models.

Common issues & troubleshooting

Do I need this instead of InteractiveString for a full prompt? Yes, practically speaking - InteractiveString's widget is a single-line field and will make a long prompt painful to edit. This node exists specifically for the multi-line case.

Should I use this or the stock multiline text node? For a plain part of your graph, either works. The pack author's own framing is that the Interactive-branded literal nodes are the ones meant to behave predictably inside the paused/click-driven sections of a workflow, so use this one there for consistency with the rest of the interactive graph.

Text looks like it didn't save after editing. Same pack-wide note as every node here: keep auto-enqueue off and the queue empty while you're editing widgets in an interactive workflow, or you risk catching a stale value mid-run.

I need to combine this text with another string (like a base prompt plus a branch-specific addition). This node only holds one static value - for joining two strings together, use InteractiveStringAppend, which the pack ships specifically to avoid a known display bug in a popular third-party string-concatenation node when used in interactive workflows.