KurutAI LoRA Selector

The KurutAI LoRA Selector is the pack's bridge node, and it's the least glamorous thing in the catalog for a good reason: it does no model math at all. It resolves a KurutAI LoRA down to a filename and hands that filename to ComfyUI's native Load LoRA node, so you keep the stock loader behavior you already know. If you've built a workflow around the native node and don't want a custom loader stepping into the middle, this is the one you reach for.

How it works

Like every node in the pack it carries the KurutAI metadata - lora_name, lora_id, artifact_id, sha256, trigger_words, and a metadata JSON blob. When it runs, it checks the same local download index the Loader uses. If the file isn't installed, you get the familiar "This KurutAI LoRA is not installed. Queue again and confirm the download" error, and the queue-time download consent does its thing. If all's well, it returns the resolved filename plus the trigger words and metadata, untouched.

The output that matters

lora_name is typed * - the pack's "connect to anything" type - which is exactly what you want here. On a native Load LoRA node, right-click the lora_name widget, choose Convert to input, and wire this output in. The native node then does the loading with its own strength_model / strength_clip widgets, and your graph stays built from stock parts.

The trigger_words and metadata outputs are there if you want them. Trigger words are a STRING you can splice into a prompt; metadata rides along as JSON. For a character LoRA on the Illustrious/Pony lineage, forgetting the trigger token is the classic reason the output "doesn't look like anything," so having them on a wire is a real convenience, not decoration.

Inputs worth knowing

The metadata fields are pre-filled when you pick a catalog item from the KurutAI sidebar; typed by hand they're plain strings with empty defaults, and an empty set fails the lookup. lora_id is what actually drives the download check; lora_name is what comes back out.

Install

Same pack, same path as every KurutAI node:

cd ComfyUI/custom_nodes
git clone https://github.com/KurutAI/KurutAI-ComfyUI.git

Or search KurutAI for ComfyUI in ComfyUI Manager. Restart. No pip dependencies to worry about.

Selector vs. Loader

The honest comparison: the Loader loads the LoRA and hands you trigger words in one node. The Selector only resolves the filename and leaves loading to the native node. That makes the Selector the less invasive choice - a workflow built around it stays portable to people who've never installed the pack's loader, because the native Load LoRA in the graph is still just the native Load LoRA.