📝 String Input

This is a 39-line node that does one thing: output a string you type into it. ArchAi3D_String_Input takes a value (a multiline text field, default empty) and passes it straight out of its STRING output. That's the entire job. If you've used ComfyUI for more than an hour you probably have three other nodes that do this already, so the only real question is why this one exists.

The answer is in the other input: name, defaulting to string_input. Per the author's docstring, the name field is "used by web interfaces to generate HTML form elements" - this node is part of the pack's web-interface integration. When a web UI builds a form from a workflow, the name becomes the form field's identifier, so a prompt value you type in a browser can flow into the graph through this node. If you're not using one of those frontends, the name field is inert metadata and value is just a manual text box.

It's a utility node, not a feature. You'd grab it because you're already in the ArchAi3d pack and want a labeled, stable string source for prompts or conditioning text - or because a web workflow you're following expects the ArchAi3D_String_Input class name specifically.

Installing it

Part of ComfyUI-ArchAi3d-Qwen by Amir Ferdos (ArchAi3d). ComfyUI Manager → search "ArchAi3d Qwen" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
cd ComfyUI-ArchAi3d-Qwen
pip install -r requirements.txt

Restart. No dependencies beyond ComfyUI itself - it's a pure pass-through. Free for personal use; commercial use needs the paid license.

The short version

If you need a string with a semantic name in a graph that's already using this pack, it's fine and it's free. If you're not using the pack's web frontend, any text node does the same job - don't install a 100-node pack for this one. There's nothing to tune: type value, get STRING, and don't expect the name to do anything locally.