Text

This one does exactly what it looks like it does: it's a box where you type text, and it outputs that text as a string. No CLIP encoding, no tags, no logic - just a labeled multiline field you can wire wherever a STRING is expected. The value isn't in what it computes, it's in what it lets you organize.

Why you'd actually use it

If your only text input is CLIPTextEncode's built-in box, every prompt lives buried inside a node that's also doing conditioning. That's fine for a simple workflow, but it falls apart once you start building prompts out of pieces - a subject block, a style block, a quality-tags block, a negative junk list - because CLIPTextEncode only gives you one box to jam it all into. Jjk Text lets you pull those pieces out into their own labeled nodes, which is exactly what you want if you're about to feed them into something like Jjk Concat to assemble a final prompt string, or if you just want to reuse the same block of text (a consistent style suffix, say) across multiple prompts without retyping it.

It's a small, obvious idea, and that's the point - it's the same pattern as ComfyUI's own built-in multiline text primitive, just given its own name in the jjk node category so it's easy to find alongside this pack's other text nodes.

Inputs and outputs

There's exactly one field:

• text - a multiline string box. Required. Type whatever you want in it.

And one output:

• text (STRING) - the contents of the box, unchanged. Wire it into a CLIPTextEncode's text input, into Jjk Concat as one of its text1–text5 slots, into Jjk Show Text to confirm what's actually in it, or into any other node that takes a string.

That's the whole node. It's not an output node, so on its own it doesn't display or print anything - it just sits there holding a string until something downstream consumes it.

Installing it

Through ComfyUI Manager: search ComfyUI-Jjk-Nodes, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/jjkramhoeft/ComfyUI-Jjk-Nodes

Restart ComfyUI afterward. There's no model to download and nothing beyond ComfyUI's own dependencies to install - it's a couple hundred lines of Python, per the author's own README ("minimal code to get a few nodes working"), so there's essentially nothing here to conflict with anything else in your environment.

Where people get tripped up

The main thing to know: because it's not an output node, wiring it up and running the queue tells you nothing about whether it actually did what you expected - you won't see the text anywhere in the UI unless you route it into a node that displays it, like Jjk Show Text, or into CLIPTextEncode where you can inspect the prompt some other way. If a downstream node is getting an empty string, check that the wire is actually connected and not just sitting near the socket - an unconnected required STRING input on some nodes will error rather than silently pass through empty text.

Beyond that, there's genuinely not much to go wrong. This is a bare-bones utility from a small personal pack (four nodes total), not something with a big install base or a pile of GitHub issues to check against - it just holds text.