LoRA Trigger Local

If you've ever loaded a LoRA, gone back to CivitAI to copy its trigger word, pasted it into your prompt, then done the exact same dance three loads later because you forgot it again - this node is for that. LoRA Trigger Local is a drop-in replacement for the standard LoRA loader that remembers the trigger word for you, locally, in a JSON file it manages on its own. Type it once, check a box, and every future time you pick that same LoRA file the trigger word is just... there.

How it works. Under the hood it's a normal LoRA loader - it takes your MODEL and CLIP, patches in the LoRA at whatever strength you set, and passes them along. The trick is what happens around that: when save_trigger_local is on and you've typed something into trigger_word, it writes the LoRA-filename-to-trigger-word pairing to a local file. Next time you select that same lora_name, leave trigger_word blank, and it auto-loads what you saved. No lookup, no CivitAI tab, no clipboard juggling.

The inputs you'll actually touch: model and clip come from your checkpoint loader like any LoRA node. lora_name is your dropdown pick from the loras folder. strength_model and strength_clip are the usual weight sliders (default 1, range -10 to 10) - for what to actually set them to, check the LoRA's own model page rather than reaching for a stock number; the old "0.5-0.8" SDXL rule of thumb doesn't generalize to newer architectures, where full-strength or higher is increasingly normal. trigger_word is where you type the word the first time; leave it empty on later runs and the saved one loads automatically. save_trigger_local (on by default) is the checkbox that makes the memory permanent - renaming the LoRA file afterward doesn't break the link. positive_prompt is optional, for everything else you want in your prompt besides the trigger word itself.

Outputs: MODEL and CLIP wire onward exactly like any LoRA loader. Full Prompt text is the trigger word and your positive_prompt already concatenated - plug this straight into your CLIP Text Encode and skip manual string-building. Only Trigger text gives you just the trigger word by itself, useful if you're combining multiple LoRAs' words yourself rather than letting one node glue everything together. PNG name reports back whichever preview image you picked, if you're using the image-browsing feature below.

There's also a select_lora_by_png field: pick a PNG from ComfyUI's input folder and the node syncs lora_name to match, so you can browse LoRAs by their preview image instead of a filename dropdown. Its tooltip is honest about the catch - it only works with ComfyUI_Custom_Nodes_AlekPet installed alongside this pack, and it's genuinely optional. Skip it and the node works fine as a plain LoRA-plus-memory loader.

Installing it: search "ComfyUI-LoRA-Assistant" in ComfyUI Manager and install from there, or cd ComfyUI/custom_nodes && git clone https://github.com/Bellzs/ComfyUI-LoRA-Assistant and restart. No models to download, no heavy Python dependencies - it's a lightweight loader plus a JSON file it writes on your machine. If you want the PNG preview picker, install AlekPet's node pack too and drop matching preview images (named after your LoRA files) into ComfyUI's input folder; without AlekPet, that dropdown just won't populate - the loader itself is unaffected.

Where this sits versus the obvious alternative: if you've spent any time in r/comfyui you've probably seen people point to rgthree's Power Lora Loader for this exact problem - it stacks multiple LoRAs in one node and its info dialog fetches trigger words straight from CivitAI. That's the bigger, better-known tool, and it's the one to reach for if you're juggling several LoRAs at once or want CivitAI's data pulled automatically. LoRA Trigger Local does one thing narrower and offline: it's a single-LoRA slot where you set the trigger word once and it's saved locally, no internet lookup required - which actually makes it the better fit for private or local-only LoRAs that were never on CivitAI to begin with.

One thing to know before it bites you: because an empty trigger_word field auto-loads the last saved value, you can't clear a saved trigger word by just leaving the field blank - you'll need to type the new (even empty-string) value and let save_trigger_local overwrite it.