凤希AI - 字符串
A text box that travels down a wire
- string
One string, many consumers
ComfyUI already has string nodes in core, and if you only need one text box you should probably use them. The reason to keep a pack-supplied one around is the same reason every plumbing pack ships its own: once a prompt, a filename prefix, or a regex needs to feed several nodes, you want a single source of truth sitting on a wire instead of the same text typed into four widgets.
FxAiString (凤希AI - 字符串) is exactly that: one value field, one STRING out, no processing whatsoever.
How it works
There is nothing under the hood. The input is a STRING widget, and the node returns it unchanged - no formatting, no substitution, no escaping. It's a constant with a socket on it, which is also why it's the safest node in this pack to trust: there's no behaviour to be surprised by.
That triviality has one genuinely useful consequence. Because it's a real node in the graph rather than a widget, its value is part of the execution hash - change the text and ComfyUI knows the downstream needs to re-run. That's how editing a single node updates every consumer at once, instead of you hunting for the fourth place you pasted the same sentence last week.
Inputs and outputs
value(STRING, default empty) - note it's a single-line field, not multiline.- Output:
string(STRING).
That's it. Wire it into a CLIP Text Encode's text input (converted from widget), a save-node filename prefix, another node's STRING parameter, or a compare node if you're checking whether a name changed.
Where it earns its place
The strongest case is a negative prompt or a shared style suffix used in three encoders. The second is the "constant that also needs to be compared" pattern: the same string feeding a text encoder and a FxAiCompare doing a == b, which is how you build a guard that only fires for a particular variant.
It's also the polite way to build a reusable workflow that a non-author will run. Every string that a person might reasonably want to change lives in one obvious node at the top of the graph, labelled, instead of being buried in step four.
Installing
cd ComfyUI/custom_nodes
git clone https://github.com/fxai666/fxai-toolkit
Restart, or install via ComfyUI Manager by searching fxai-toolkit (registry publisher fxai). The pack pip-installs soundfile and psutil on first import; this node needs neither, and no model files.
Worth knowing before you install a ~200-node Chinese-language pack just for a string constant: the same pack has a FxAiMultiLineTextLoad family for actual prompt files, and this node is deliberately the minimal one.
Where it bites
Single-line. multiline is false, so a long prompt becomes a horizontal scrollbar and a bad time. For anything paragraph-length use a multiline node - core's PrimitiveStringMultiline or this pack's prompt loaders.
No string operations. No concatenation, no formatting, no joining a filename out of a prefix and a loop index. You'd need a node that actually computes text for that; this one only carries it.
Type-strictness downstream. STRING is STRING. Feeding it into an INT socket does nothing useful even if the text is digits - ComfyUI's link validation will refuse it, or, if the target socket is a wildcard, you'll get a string where a number was expected. FxAiSimpleMath will happily take digits off a wildcard and hand you an int, which is the usual workaround.
Not in the menu. Each node in this pack is registered individually inside try/except, logging ❌[凤希AI] 节点加载失败 on the console when an import fails - one broken module removes one node, quietly. Console first, restart second.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| value | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| string | STRING | — |