Textbox

Textbox does exactly what the name promises and nothing more: a standalone multiline string box you can drop anywhere in a graph and wire into anything that wants text. That sounds almost too simple to write up, but the reason it exists is real - ComfyUI's built-in CLIPTextEncode bundles its text field into the encoder node itself, so if you want one prompt feeding two encoders, or a text value you can move around and label independently of where it's consumed, you need a text source that lives on its own. Textbox is that source.

It shows up in the wild for exactly this reason. One Reddit workflow running sixteen checkpoints off a single shared prompt used a "Textbox Chibi-Nodes" as the one positive prompt box, fanned out to every sampler with rgthree's Seed Everywhere and cg-use-everywhere's Anything Everywhere doing the wiring. That's the pattern: one box, many consumers, instead of retyping or copy-pasting the same prompt into a dozen encoders.

The inputs and outputs that matter

• text - the multiline field you actually type into. That's the whole required input.
• passthrough - an optional second multiline string. There's no tooltip on this one and the name is the only clue; it reads like a way to route another string through the same node rather than something that alters the primary text, but I won't pretend I've traced the exact plumbing. If you don't need it, ignore it - the node works fine with just text.

The single output is text, a STRING, which you plug into a CLIPTextEncode's text socket (right-click it and convert the widget to an input first), or into any other Chibi node that takes a STRING - TextSplit, LoadEmbedding, Wildcards' optional text, ImageAddText's caption field.

One detail worth knowing: this node is flagged is_output_node, meaning ComfyUI will always run it even if nothing downstream is connected. Practically that just means you can leave a Textbox sitting unwired as a scratchpad and it won't get pruned out of the execution graph.

How to install it

Two ways, same result:

• ComfyUI Manager: search "ComfyUI-Chibi-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/chibiace/ComfyUI-Chibi-Nodes/, then restart.

There's nothing else to it - no models to download, no Python dependencies beyond what ComfyUI already ships. The whole pack is pure node logic. After restart, Textbox and its siblings show up under the Chibi-Nodes category in the add-node menu (this one specifically under Chibi-Nodes/Text).

Worth setting expectations up front for the whole pack, since it applies to every node in it: the README calls these "experimental nodes" and jokes that version 2 shipped "with more bugs." That's the author being straight with you rather than a red flag - it's a small personal utility pack, not a maintained-by-a-team collection, so don't expect frequent updates or exhaustive docs. Textbox itself is about as low-risk as a node gets; there's no logic to break.

Common issues

The only real trap is forgetting to convert the text widget to an input when you want to feed it from somewhere else - by default it's a widget you type into directly, and ComfyUI won't auto-wire a string output into it until you right-click and switch the socket mode. If a downstream CLIPTextEncode still shows its own inline text box instead of accepting your Textbox's output, that's the fix. Beyond that, this is about the least troubleshooting-prone node in the whole pack - it stores a string and hands it back out.