Text Box
A plain multiline string node for prompt fragments
- text
A multiline text field that outputs whatever you type. That's it - the humble primitive every prompt-building graph is made of. You type tags or prose in, a STRING comes out, and it goes wherever a text input is expected: a CLIP Text Encode, a combiner, a switcher.
It's unglamorous, but it's the node the rest of the pack's text tooling is designed around. mirabarukaso's whole approach to prompts is modular - keep each concern (quality tags, character, pose, style) in its own box and glue them at the end with a Text Combiner. Text Box is that box. Having a clean, dedicated string node means your graph reads as a set of labelled fragments instead of one opaque prompt field.
How it works
There's no mechanism to explain. You type into the text widget; the node outputs that exact string on its text output. Multiline is on, so line breaks are preserved, which matters if you're storing something you want formatted rather than one long comma run.
The input that matters
- text - the multiline string you type. Output is a single text carrying the same value.
Where it fits
This is a source node - it sits at the start of a text chain. Typical pattern: one Text Box per prompt concern, all of them feeding a Text Combiner (2 or 6) that assembles the final prompt, which then goes to your encoder. Splitting a prompt across several Text Boxes is what lets you swap one part without disturbing the others, and it's also handy for parking a favorite fragment - a quality prefix you reuse, a tricky negative - somewhere you can see and copy it.
Why use this over ComfyUI's built-in primitive string node? Mostly consistency: if the rest of your graph is Mira text nodes, keeping the source node in the same family makes the whole chain read cleanly and behave predictably when combined. It's also a good place to stash the little reusable bits - the model's required quality tags, a negative you always want - as labelled boxes you can wire in and out without retyping. There's no functional magic here; it's the plain, reliable string source the modular approach is built on.
Install
ComfyUI Manager → Custom Nodes Manager → search ComfyUI_Mira → Install → restart. Or by hand: cd ComfyUI/custom_nodes && git clone https://github.com/mirabarukaso/ComfyUI_Mira.git, then restart. If the pack errors on load, run pip install -r requirements.txt in its folder. No downloads.
Common issues
There's essentially nothing to go wrong with a text box. The one thing worth a thought is separators when you chain it: if this box's contents get combined with another fragment downstream, end the line with , so the tags don't collide at the join. Other than that, this node does exactly one thing and does it reliably - which, honestly, is the point of having it.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| text | STRING | — |