Nodes/ComfyUI-KikoTools/Text Encode for Sampler Params
ComfyUI Node

Text Encode for Sampler Params

The XYZ-Plot Prompt Encoder, Kept Alive

By ComfyAssetsΒ·Created about a year agoΒ·Updated 2 months agoΒ· 19
Text Encode for Sampler Params
  • clip
  • conditioning
β—„textSeparate prompts with at least three dashes --- Like soβ–Ί

If you've ever used cubiq's ComfyUI_essentials, you've seen this node - it was the Text Encode node used for XYZ-plot and batch testing. ComfyUI_essentials went into maintenance mode, and this is the KikoTools reimplementation, part of the pack's "xyz-helpers" family. Same job: take several prompts, encode them all, and hand back a single conditioning output that batch/XYZ tooling can iterate over.

How it works

You type multiple prompts into one multiline field, separated by a line of dashes (the default example literally shows --- between them, and the splitter also accepts ***, ===, and ~~~). The node validates the format, splits the text into individual prompts, and encodes each one separately with the CLIP model you connect. The result is a special conditioning bundle that downstream batch machinery - the pack's Flux Sampler Params and friends - knows how to unpack into one run per prompt.

That's the key mental model: this is not a replacement for the plain CLIP Text Encode node in a normal text-to-image graph. It's a batch-oriented encoder. Wire it up by itself and you'll get a conditioning that most samplers won't know what to do with. It earns its place when you're doing parameter sweeps - prompt A vs prompt B vs prompt C, all other settings held fixed - which is exactly how you figure out which phrasing actually moves the needle.

It supports the prompt syntax you're used to from other ComfyUI text nodes - wildcards, emphasis, and dynamic prompts - because the text field is marked as a dynamic-prompt source, so {red|blue} style alternation works.

Inputs and outputs

Only two inputs, and that's the appeal:

  • text - multiline STRING. Your separated prompts.
  • clip - the CLIP model, from your checkpoint or a CLIP loader.

One output: conditioning.

Installing it

Part of ComfyUI-KikoTools. ComfyUI Manager β†’ search "ComfyUI-KikoTools" β†’ Install β†’ restart, under ComfyAssets β†’ xyz-helpers. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/ComfyAssets/ComfyUI-KikoTools.git
cd ComfyUI-KikoTools
pip install -r requirements.txt

Restart ComfyUI.

Gotchas

The one thing to watch: if you also have the original ComfyUI_essentials installed, the two packs share this lineage and can present overlapping node names - people have hit node-conflict errors after installing KikoTools alongside it. ComfyUI Manager usually surfaces the conflict; if you see weird "duplicate node" errors, disable one of the two packs. And remember the conditioning output is batch-shaped: feeding it straight into a plain KSampler without the matching xyz-helper plumbing is the "I connected it and got a weird error" story. Pair it with the pack's other xyz-helpers (Flux Sampler Params, LoRA Folder Batch) where it's actually meant to live.

Category🫢 ComfyAssets/🧰 xyz-helpers

Inputs (2)

NameTypeDefaultDescription
textSTRINGSeparate prompts with at least three dashes --- Like soMulti-line text with --- separators between prompts
clipCLIPCLIP model for text encoding

Outputs (1)

NameTypeDescription
conditioningCONDITIONINGβ€”