🔶 Text Prompt Clip Endcode +Lora

This is the LoRA-aware sibling of Chaosaiart's plain Text Prompt Clip Encode: same two-textbox layout for positive and negative prompts, but it also takes a model and a LoRA, patches them together, and hands back a LoRA-modified model alongside your two conditioning outputs. Where the plain version replaces two CLIP Text Encode nodes, this one replaces a LoRA loader and two encode nodes - matching the pack's own "How to Use Loras" workflow, which pairs this node with the Info Display node to also surface the LoRA's trigger words.

How it works

The mechanics are standard LoRA application: the LoRA's weight deltas get merged into the model and CLIP before anything gets encoded. Order matters here - a LoRA has to be applied before text encoding for its influence to actually reach the conditioning, and bundling both steps into one node is exactly what makes it impossible to accidentally do that backwards.

The trigger-word piece is worth calling out on its own. The README credits idrirap's ComfyUI-Lora-Auto-Trigger-Words node for the underlying idea: a LoRA's trigger tags and how often each was used live in the file's own metadata, so the pack reads them back out rather than making you dig up the CivitAI page. It's a smaller, more manual version of what rgthree's Power Lora Loader does with a right-click menu that fetches trigger words and links straight to CivitAI - Chaosaiart's approach only surfaces what's actually baked into the file, so it won't help on a LoRA that never had trigger words embedded to begin with.

Inputs and outputs

• model (required, MODEL) and clip (required, CLIP) - from your checkpoint loader.
• lora (required, LORA) - a loaded-LoRA object from an upstream Chaosaiart lora-loading node, not a plain filename dropdown on this node itself.
• positiv_txt / negativ_txt (required, STRING, multiline) - your two prompts.

Outputs: MODEL (the patched model - feed it to KSampler), POSITIV and NEGATIV (CONDITIONING).

Note what's not here: there's no strength slider on this node itself. Wherever the lora input's strength gets set lives on the upstream node that produces it, not on this one.

Installing it

ComfyUI Manager → Install via Git URL → https://github.com/chaosaiart/Chaosaiart-Nodes. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/chaosaiart/Chaosaiart-Nodes, restart. Linux: also pip install opencv-python and pip install tqdm per the README. No model downloads for the pack itself - bring your own checkpoint and LoRA files.

Where people get burned

The general LoRA troubleshooting checklist applies here same as anywhere else in ComfyUI:

• Base model mismatch. A Flux LoRA won't run on SDXL; Pony/Illustrious/SDXL share enough architecture to look selectable together but often aren't cross-compatible in practice.
• Weight too strong. Default 1.0 frequently overshoots - try 0.5–0.8 if you're seeing artifacts or the image looking baked.
• Missing trigger words. If the LoRA's effect seems weak or absent, check whether it actually needs a specific trigger phrase in the prompt - that's the whole reason this node bothers extracting them.
• Stacking more than one LoRA isn't this node's job. It applies exactly one lora input. If you want to chain several, that logic has to live in whatever node produces the lora value upstream - check that node for chaining support before assuming this one is broken.