Text _O

In the middle of a ComfyUI graph you'll eventually want a plain prompt you can edit on the canvas and route to a CLIP Text Encode - something you can double-click, type into, and not have to dig through node settings to change. That's Text _O: one big multiline text field, one STRING output. Nothing else. It's in O/utils from the Quality of Life Suit pack, and it's the node you'll reach for when a workflow asks you to "add a prompt node" and the pack's grouping has you sorted.

ComfyUI's core already ships a primitive text node these days, so this isn't revolutionary. But this pack puts its utils under the O/ umbrella, and if you're already building in that pack's ecosystem - say, your prompt starts life in a ChatGPT node, gets cleaned by Trim/Replace, gets split by QOL Split String, and lands here before the encoder - Text _O is the tidy end of that chain. It's a pass-through in the truest sense: the source literally returns what you typed (with a trailing space appended, which you'll never notice).

Using it

• text - the only input, a multiline string. That's the whole node.
• Output: one STRING.

Wire that output into a CLIP Text Encode (the text port on the positive side) and you have a prompt you can tweak without touching the node graph. Because it's just a string value, you can also feed it into anything else that eats text - a Concat Text _O for assembly, a saveTextToFile _O for logging, or straight into a prompt-scheduler if you're being fancy.

Installing

It's pack-wide: ComfyUI Manager → search ComfyUI-QualityOfLifeSuit_Omar92, or:

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

Then restart ComfyUI - a browser reload won't register new nodes. No extra dependencies for this one; the pack only pulls in optional libraries (OpenAI, pygit2) if you touch those features.

Any traps?

Honestly, no. It's a text box. The only mild confusion is why it exists next to ComfyUI's own primitive - answer: category organization and pack consistency, and the fact that some downloaded workflows insist on it, so having it installed means those workflows load without "missing node" errors. Drag a workflow PNG onto the canvas and a missing Text _O is exactly the kind of thing that fails to reconstruct - this pack's utility nodes exist partly so those shared graphs just work. That alone earns it a place in your install.