Diffusion Model Selector Resident

This one's the unglamorous utility of the pack, and unglamorous is exactly why it's handy. Diffusion Model Selector Resident takes a model name and returns the absolute path to that file as a plain string. No loading, no VRAM, no residency magic - it just resolves a name you picked from a dropdown into a full path you can wire into anything that wants a path.

It mirrors the selector behavior in Kijai's KJNodes, with one extra trick: alongside your diffusion_models folder, it also lists text_encoders entries whose filename contains "connector". That's a quiet nod to LTX-Video, which keeps its text-encoder connector models in the text-encoders folder. So this is the selector that can hand you the path to your diffusion model or your LTX-Video connector from one dropdown.

The interface is about as minimal as a node gets:

• model_name - the only input. A dropdown of your diffusion models plus any "connector" files in text_encoders.
• model_path - the only output. A STRING with the absolute path.

So why reach for it? ComfyUI gives you paths when you use a loader node directly, but plenty of custom nodes take a STRING path input - and few things are more annoying than hand-typing an absolute path that changes when you move your models folder. Drop this node in, pick the model once, and the path stays correct everywhere it's wired. It also pairs naturally with this pack's own loader: Diffusion Model Loader Resident takes a model_name enum, but if you're building a graph that needs the same model referenced in multiple places, a shared resolved path is a clean way to do it.

Install it with the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/xmarre/ComfyUI-GPU-Resident-Loader
cd ComfyUI-GPU-Resident-Loader
pip install -r requirements.txt

Or search "comfyui-gpu-resident-loader" in ComfyUI Manager and restart.

The one thing to know before you trust the output: it's a path, not a load. The file doesn't have to exist until something downstream actually opens it, so a stale path won't error here - it'll error at the consumer. And since it lives in the GPU Resident Loader pack, it comes with all of that pack's startup patches whether you use them or not. If all you want is a path resolver and you already run KJNodes, their original selector does the same job with one less pack installed. But if you're in this pack anyway, this is the cleanest way to get exact paths out of a dropdown.