Download LoRA (Model Manager)
Pull a LoRA off the server into your normal loras folder — no cache games
- lora_name
- model_ref
Here's the thing about this pack's caching: the loader nodes save everything into their own private cache directory, which means only their loaders can see it. The rest of ComfyUI is oblivious. Download LoRA (Model Manager) fixes that asymmetry. Instead of caching, it downloads a LoRA directly into ComfyUI's standard loras folder - so it shows up in the plain, boring, stock Load LoRA node and every other tool that reads that folder.
Why you'd reach for it
Say you pull a LoRA from your Model Manager server, love it, and want to use it in a workflow that doesn't have a Model Manager node in it - or you want it available to the core loader, another pack's stack loader, or a LoRA training UI. Dragging a file out of the cache by hand is a chore; this node does it properly: it fetches the file, names it cleanly, and drops it where ComfyUI already looks.
It's also smart about duplicates: before downloading, it scans the loras folder for a file already prefixed with this model's {model_id}_{version_id}_ and skips the download entirely if one exists.
Inputs: lora_name, the server-side LoRA dropdown (same modelId@versionId:name values, same (not connected) until you authenticate). Outputs: lora_name (the local filename it saved - wire this into a stock Load LoRA node's lora_name input) and model_ref (the original server selection, in case you want to keep tracking where it came from).
What it does NOT do
It doesn't apply the LoRA to anything. There's no model input here - it's a downloader, not a loader. After it runs, the LoRA is on disk in ComfyUI/models/loras, ready for any ordinary loader to pick up. And because it's writing to the standard folder, Clear Cache (Model Manager) won't touch it - which is exactly the point.
Install
ComfyUI Manager (search comfyui-model-manager-nodes) or:
cd ComfyUI/custom_nodes
git clone https://github.com/blackpaw-studio/comfyui-model-manager-nodes
cd comfyui-model-manager-nodes
pip install -r requirements.txt
Restart and connect (Connect to Model Manager button, or config.yaml / MODEL_MANAGER_API_URL / MODEL_MANAGER_API_KEY env vars). Dependencies: requests and pyyaml.
Troubleshooting
(not connected)- authenticate first; bad keys get 401'd and the dropdown stays empty.- The file appears with a long prefixed name like
123_456_style.safetensors. That's deliberate - the prefix is how the node recognizes already-downloaded files and skips re-fetching. You can rename it afterward if it bugs you; just don't expect the dedupe check to find it under a new name. - It downloads every time? Only if the prefix check fails - e.g., you renamed the file. Otherwise it's a one-shot.
A small, specific tool, and a useful one if you mix Model Manager workflows with everything else in your install. One run, one file, zero cache confusion.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| lora_name | COMBO | 1 options: (not connected) |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| lora_name | * | — |
| model_ref | * | — |