Nodes/Sage Utils/Collect Keywords From LoRA Stack
ComfyUI Node

Collect Keywords From LoRA Stack

Your trigger words, ready to paste into the prompt

By arcum42·Created 2 years ago·Updated 22 days ago· 33
Collect Keywords From LoRA Stack
  • lora_stack
  • keywords

Every LoRA carries a set of trigger words - the rare-token keywords it was trained on, without which it barely activates. And the most common workflow failure with LoRAs isn't the weight, it's forgetting the trigger words entirely: you stack three LoRAs, generate, and wonder why nothing changed. Collect Keywords From LoRA Stack exists to make that failure hard: it walks every LoRA in a stack and hands you the combined keywords as one string, ready to drop into your prompt.

Input is a single LORA_STACK - the same stack data type produced by the pack's Simple Lora Stack / Triple Lora Stack nodes and consumed by Lora Stack Loader. The output is a keywords string that concatenates the trigger words for every entry in the stack. Wire that straight into your positive prompt (or into a Join Text node to combine with your main prompt) and you've permanently automated the "did I remember the triggers" step. Since the stack knows which LoRAs are enabled and their weights, the keywords follow what's actually active.

How does it know each LoRA's keywords? The same machinery behind the rest of the pack's LoRA tools: it looks up each LoRA's Civitai info - hashed locally, then fetched and cached in sage_cache_hash.json / sage_cache_info.json under comfyui/user/default/SageUtils/. LoRA authors list their trigger words on their Civitai pages, and that's where these come from. Caveat in two parts. First, the cache needs to have seen the LoRA: an unfamiliar file gets a hash and a lookup on first use, so a brand-new download may be sparse until that happens. Second, and more importantly, not every LoRA author fills in the trigger-word field - some list none, some bury them in the description. If a LoRA's keywords come back empty or wrong, that's a data problem on Civitai's side, not a node bug, and you'll want to check the model page.

This is a genuinely useful automation, and it pairs well with the pack's LoRA Stack Info Display (the pretty markdown version) if you want to see weights and links alongside. One is for humans to read; this one is for your prompt.

Install

ComfyUI Manager → search Sage Utils → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/arcum42/ComfyUI_SageUtils.git
cd ComfyUI_SageUtils && pip install -r requirements.txt

Restart ComfyUI. Only dependency is dynamicprompts; no model files to fetch from the pack itself. If you're not using the Sage Utils LoRA stack system yet, you'll need to build your stack with Simple/Triple Lora Stack nodes first - this node only works on stacks it knows.

CategorySage Utils/lora

Inputs (1)

NameTypeDefaultDescription
lora_stackLORA_STACK

Outputs (1)

NameTypeDescription
keywordsSTRINGCollected keyword string extracted from the LoRA stack.