CRZ String

CRZ String is the text input of the ComfyUI-CRZnodes dashboard pack: a small node that holds a string and outputs it as a STRING. If that sounds like it does nothing, that's because it does - and that's exactly the point. The stock ComfyUI text nodes are fine, but they're editor widgets buried in a node's body. This one is built to sit on a dashboard where the text you most often change - a prompt fragment, a filename prefix, a negative-prompt section - is visible and editable at a glance.

It was added in response to community feedback, which is how a lot of this pack grew. Someone on the r/comfyui launch thread asked for string support; the author's reply was a screenshot captioned "String node added (:". Small pack, responsive author, feature shaped by users - that's the pattern here.

How it works

The text lives in a hidden widget (a STRING with a default of ""), and the frontend draws the node's own editable field with a name label you can rename. Double-click or click into the text area to edit it directly on the canvas. On the backend, main() just reads the hidden widget and returns it - one string in, one string out, no processing, no magic.

The output is text (STRING). It plugs into anything that wants a string: prompt concatenation, filename prefixes, wildcard processors, text-encoding chains.

The input and output that matter

• No required or optional inputs - the text is stored in the hidden widget.
• text (output, STRING) - whatever you typed, ready to wire into text consumers.

One output, one hidden field. Double-click the label on the left to rename the node so your dashboard reads "Subject" or "Prefix" instead of "String."

Installing it

Standard pack install: ComfyUI Manager → search ComfyUI-CRZnodes → install → restart. No requirements, no models.

cd ComfyUI/custom_nodes
git clone https://github.com/CoreyCorza/ComfyUI-CRZnodes.git

How it fits the dashboard idea

The dashboard philosophy of this pack is "the things you touch live where you can see them." A CRZ String holding your style prompt fragment sits next to the sliders and toggles that shape the same generation, so editing the whole workflow happens in one row instead of across five node bodies. Combine it with the CRZ Custom Dropdown for options (pick the fragment) and the CRZ Label for headings, and you've got a control panel that reads like a form.

Gotchas

It's about as fault-tolerant as a node gets, but two small things. First, the string is stored in the hidden widget, which means it persists into the workflow JSON - if you share a workflow, whatever text you typed goes with it, for better or worse. Second, if you're chaining strings into a prompt, remember this node outputs the raw text exactly as typed: trailing spaces and all. Trim or format upstream before you feed it to a text-encoder if exact prompt hygiene matters to you. Neither is a bug - they're just the two ways a "does nothing" node can still surprise you.