NGs TextBoxes - x2

Same idea as NGs TextBoxes Simple, just two of them stacked in one node body instead of two separate nodes eating up canvas space. The README's pitch for the family covers exactly this use case: "Need nodes for simultaneous handling of 2 or even 3 different texts? No problem." It's a good fit for paired fields you tend to edit together and want visually grouped - a positive/negative pair, a title/caption pair, two variants you're comparing side by side.

None of this is functionality core ComfyUI is missing, exactly - you could always place two separate multiline String primitives and get the same two outputs. What you're buying with a node like this is purely organizational: one node to move, one node to collapse, one node whose title tells you at a glance that these two fields belong together conceptually. That's a small thing on a five-node test graph and a genuinely useful thing on a sprawling production workflow you'll be reopening for months.

How it works

Two entirely independent multiline fields. There's no interaction between them - text_1 doesn't affect text_2's output or vice versa. This isn't a join or a combine; it's just two Simple TextBoxes sharing one node.

The reason this is worth having as a dedicated node rather than two separate NGs TextBoxes Simple instances comes down to graph real estate and readability. Two loose text nodes float independently - you have to trace two separate wires and remember they're related. Bundled into one node, they read as a pair at a glance, which matters more than it sounds like once a workflow has thirty or forty nodes on the canvas and you're trying to eyeball what feeds what.

The inputs and outputs that matter

• text_1, text_2 - both multiline, both required.

Outputs: text_1, text_2 - two separate STRING outputs, unconnected to each other.

How to install it

ComfyUI Manager: search "NeoGriever," install, restart. Manual:

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

then restart. No dependencies to worry about.

Common issues & troubleshooting

Expected a combined output. This node keeps text_1 and text_2 as two separate outputs by design - it won't merge them for you. If you actually want them joined into one string, wire both into NGs TextBoxes Join (or NGs String Squisher) afterward.

Need a third field. Don't bolt a Simple TextBox on next to this one - jump straight to NGs TextBoxes x3, which is the same idea with one more slot built in.

Only using one of the two fields. Nothing stops you from leaving text_2 empty if you only need one field right now - it'll just output an empty string on that socket. That's a reasonable way to future-proof a graph you expect to need the second field in later, without having to swap nodes when that day comes.