ComfyUI-AICoser Text Box

Some nodes do one thing and do it well. AICoser_TextBox does one thing: it's a multiline text field that takes a string in and gives the same string out. That sounds pointless until you remember that ComfyUI prompts are built from text that needs to flow between nodes, and every workflow needs a place where a human actually types the words.

You'll reach for it in the same places you'd reach for the core PrimitiveStringMultiline: as the on-graph source for your positive prompt, as the input to a template node like this pack's AICoser_PromptTemplate, or as a value you can "convert to input" so other nodes can feed it instead of you retyping. Where it earns its keep in practice is organization - a workflow with a labeled TextBox sitting at the top saying "SUBJECT" and another saying "NEGATIVE" reads better than raw strings scattered through the graph.

How it works

There's no real magic here, which is the point. The node declares a required multiline STRING input, passes it straight through, and - the one clever bit - implements IS_CHANGED by hashing the text. That matters because ComfyUI's cache decides whether to rerun a node's branch by checking if its inputs changed; with a plain pass-through, changed text can fail to propagate. Hashing forces a correct rerun whenever you edit the box.

Inputs and output

• text - required, multiline. The only input; type your prompt (or whatever string you need) here.
• Output: text (STRING) - the same string, ready to wire into a CLIP Text Encode, a template node, a filename builder, anything that eats text.

Installing it

Part of ComfyUI-AICoser-Tools, installed the same way as the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/aicoser-sister/ComfyUI-AICoser-Tools

Restart ComfyUI, or install via ComfyUI Manager by searching "ComfyUI-AICoser-Tools". No dependencies beyond ComfyUI itself.

Common issues

• "Why does this exist when ComfyUI ships a text primitive?" - Fair question. It genuinely overlaps with PrimitiveStringMultiline. The practical differences are marginal: if you're already using core primitives and they work, you don't need this. It earns its place in this pack's own workflows, where it pairs naturally with the template node and the queue-based batch nodes.
• Nothing happens when I type - you need to actually wire the text output somewhere. A TextBox that isn't connected to anything is just a notepad.

Honest take: it's a utility node, not a feature. Grab it because it's already in the pack and it makes prompt-building graphs tidier - don't install the whole pack just for this one.