Ard Text Box
A multiline text box, and when it's still the right one to grab
- string_out
ARD Text Box is exactly what it says on the tin: a multiline text box that takes a string in and hands the same string back out. That's the whole mechanism - the source is literally a pass-through, one return statement. You type, it carries. So the honest question isn't "what does it do," it's "when is a pass-through node this plain worth using."
The answer, these days, is mostly "when you're already in this pack." ComfyUI ships a built-in Text (multiline) node now, so if you're starting a workflow from scratch, the stock node covers you. But this pack's nodes - ARD Dual Prompt, ARD Prompt Travel, ARD Load Image, the Control Box - expect to receive their text as STRING inputs, and this is the node the pack's own workflows reach for to feed them. When a shared workflow loads and asks for ARD_TEXT_BOX specifically, that's what you need.
The inputs and output
One required input, one output, no surprises:
input_text- aSTRINGwithmultilineon, so you get a big text area instead of a single-line box. It also has thedynamicPromptsflag set, meaning if you've got the Dynamic Prompts extension installed, wildcards like{red|blue|green}in that field will actually expand. That's a genuinely nice touch you don't get on the stock Text node without setting it up yourself.string_out- the same text, verbatim. No trimming, no formatting, nothing added.
Wire string_out into any STRING input further down: a prompt, a filename prefix, a metadata field. If you're doing batch work with a changing prompt, keeping it in one labeled box at the top of the graph beats digging through KSampler widgets.
Install
Part of the ComfyUI-Ardenius pack. ComfyUI Manager → search "Ardenius" → install ComfyUI-Ardenius, or:
cd ComfyUI/custom_nodes
git clone https://github.com/ArdeniusAI/ComfyUI-Ardenius
Restart and it's under Ardenius ("Ard Text Box"). Zero dependencies you didn't already have, no models, no config.
The honest take
If you're not using the rest of the Ardenius ecosystem, the stock Text node does the same job and you can ignore this one. If you are - or you just like having a clearly-labeled prompt box that doesn't get tangled in widget defaults - this is a perfectly serviceable text passthrough, and the dynamic-prompts flag is the one feature where it's actually ahead of the built-in. It's a utility node, not a headline. That's fine. Sometimes the plumbing deserves its own page.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| input_text | STRING | enter your text here |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| string_out | STRING | — |