VRGDG_TextBox

VRGDG_TextBox is a text box. That's it. No models, no GPU work, no hidden agenda - which makes it one of the more useful nodes in the pack, because it does the one thing ComfyUI keeps making awkward: getting a blob of text into your graph as a reusable value.

In VRGameDevGirl's music video workflow, text travels everywhere - lyrics, scene concepts, JSON of prompts, filenames. This node is the clean way to drop a chunk of text into that plumbing and, if you need it, get it back out as structured JSON. It's the sort of utility node you don't think about until you're rebuilding a workflow from scratch and realize you've been pasting lyrics into a prompt box that wasn't meant to hold them.

How it works

Two inputs:

• text - a multiline field. Paste whatever you're carrying.
• output_mode - a dropdown with two choices: string or json.

And two outputs, one per mode:

• text_output - the raw string, straight through.
• json_output - the text parsed (or presented) as JSON, for nodes that expect a JSON-typed wire.

The mode switch is the entire trick. Set it to string and you've got a plain passthrough; set it to json and the node hands its downstream a JSON value, which matters because ComfyUI distinguishes JSON-typed wires from plain strings in custom node schemas. If a downstream node only accepts JSON, a plain string input won't connect - this node is how you bridge that.

It's also just handy as an always-connected text source when you're iterating: type in one box, and every downstream node that reads it updates in place, instead of you hunting through five prompt widgets to change one lyric.

Installing it

Part of the VRGameDevGirl Video Enhancement Nodes pack (vrgamegirl19/comfyui-vrgamedevgirl). Through ComfyUI Manager, search vrgamedev and hit install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

Restart ComfyUI. Zero extra dependencies for this node and no models to fetch - it's pure text plumbing.

Common issues

json_output doesn't connect to something. Check output_mode. If it's set to string, the node only exposes text_output as usable; switch the mode to json and the JSON output comes alive. They're two modes of the same node, not two simultaneous outputs.

Text with line breaks looks mangled downstream. That's usually the consumer node being picky about newlines, not this node - pass it through a prompt or conditioning node that accepts multiline input.

If you're the type who likes minimal, legible graphs, this node will quietly earn its place. It's not glamorous. It's a box you type in. And every so often that's exactly what a workflow is missing.