EmAySee Lora File Picker

A LoRA dropdown that doesn't apply anything

EmAySee_LoraFilePicker does one thing and does it without touching a single weight: it gives you a dropdown of every LoRA in ComfyUI's loras folder and hands you the filename and the absolute filepath as two plain strings. No model, no clip, no patching. If you want to apply a LoRA, this isn't the node - you pair it with something that takes a string name, like the pack's EmAySee_LoraApplier.

So why does this exist? Because a lot of LoRA tooling wants the name or the path as data, not a widget. The standout use is the EmAySee_LoRAMetadataExtractor, which needs a real filesystem path to a .safetensors file - and the full_filepath output here is exactly that, computed for you from a friendly dropdown. It's the bridge between "pick a file in the UI" and "do something file-system-shaped with it," which is a genuinely common need that core ComfyUI leaves you to cobble together.

How it works

Mechanically it's trivial: it reads the loras list via ComfyUI's folder system, prepends a "None" option so you can explicitly select "no LoRA," and exposes the dropdown. On execution it returns the relative filename (my_lora.safetensors, including subfolders if you keep organized lora dirs) and the resolved absolute path.

Inputs and outputs

• lora_name - the dropdown, listing every .safetensors/.pt in your loras folder plus None.

Outputs (both STRING):

• filename - the relative name, e.g. styles/dark_ink.safetensors. Feed this to anything that wants a lora folder-relative name, like EmAySee_LoraApplier's lora_name.
• full_filepath - the absolute path on disk. Feed this to file-based nodes like EmAySee_LoRAMetadataExtractor.

Install

Part of ComfyUI_EmAySee_CustomNodes:

cd ComfyUI/custom_nodes
git clone https://github.com/EmAySee/ComfyUI_EmAySee_CustomNodes
# restart ComfyUI

Or ComfyUI Manager → "ComfyUI_EmAySee_CustomNodes". No dependencies, no model downloads - it only reads your lora folder listing.

Gotchas

The one real trap: choosing between filename and full_filepath matters and it's easy to wire the wrong one. String-name consumers (LoraApplier) want filename; anything doing its own os.path or safe_open (the metadata extractors) wants full_filepath. Mix them up and you either get a silent skip or a "file not found" error string. Also note the dropdown is built from the loras directory at node-construction time - if you drop a new LoRA in while ComfyUI is running, refresh/reload the node (or restart) or it won't show up. It's a picker, not a batcher: no "iterate all loras" mode, which is what you'd want for sweep workflows, so that still means graph-level looping.