LORA Select

LORA Select is a one-trick node, and the trick is decent: it gives you a dropdown of every file in your loras folder and outputs the chosen filename as a string. That's it. No loading, no patching, no strength. You wire the string into a loader that accepts a LoRA name - typically a standard Load LoRA or a pack like the Unified Loader - and suddenly the LoRA choice lives in one tidy place instead of buried inside a loader's widget.

This is the "plain" variant, which means the dropdown lists only real filenames. Its sibling PgUniLORASelect ("LORA Select (Uni)") prepends a none option so you can explicitly turn the slot off, which is what the Unified Loader expects. Pick your flavor accordingly.

How it works

At import time it asks ComfyUI's folder_paths registry for loras (with fallbacks to lora and lora_models keys, in case another pack renames things). The list is frozen into the dropdown, and process() just returns whatever you picked. Mechanically it's the same pattern as every other PG selector - it exists to keep model choices out of loaders that are already crowded with widgets.

Why bother when you can just pick the file in the loader's own dropdown? Two reasons. First, routing: if you're building a workflow where the same LoRA feeds several places, or where a LoRA name needs to reach a node that only takes a string input, this makes the wire explicit. Second, swapping: change one dropdown and every consumer of that wire follows. It's the "selector as a variable" pattern that PG Nodes applies across checkpoints, VAEs, samplers, and so on.

The single input

• lora_name - dropdown over your LoRA files. Output is that same string on the lora_name output. That's the entire API, and there's nothing to get wrong.

Install

Part of PG Nodes, so one install covers it:

ComfyUI Manager → search "PG Nodes" → Install → restart

Manual: git clone https://github.com/GizmoR13/PG-Nodes into ComfyUI/custom_nodes (rename the folder to PG-nodes), restart. It shows up under PG/Select. No model files, no dependencies.

Common issues

• Just added a LoRA and it's missing. The dropdown is built at import time. Restart ComfyUI (or hit the reload button on the frontend) and it appears.
• Empty dropdown. If your loras folder is empty or the key is oddly configured, the list is empty rather than erroring. Drop a LoRA in models/loras and reload.
• Wrong output type confusion. The output is a plain string of the filename. It won't plug into a MODEL or CLIP input - it feeds name-based inputs. If you find yourself staring at a red wire, that's the cause.

Be honest about what this is: a utility for tidier graphs, not a feature. If you only ever use one LoRA per workflow, you don't need it. If you swap models constantly or feed names into a combined loader, it earns its place. The selector family is the unglamorous but genuinely handy part of the PG pack.