Ino Get Lora Config

LoRAs in ComfyUI-InoNodes aren't just files you drag into a loader. The pack keeps a catalog of them - with IDs, trigger words, base models, download locations, and recommended strengths - and hands them around as JSON cards. Ino Get Lora Config is the node that looks a LoRA up in that catalog: you pick it by name or by ID, optionally override the strengths, and out comes the same card shape the whole sampler system speaks.

It's one of the InoSamplerHelper nodes, and it's the read side of the pair whose write side is Ino Create Lora Config. Where the create node builds a card from scratch, this one retrieves a pre-existing one.

The inputs

• lora_name - a dropdown of LoRA names. The tooltip is blunt: "The name of the LoRA."
• lora_id - a dropdown of IDs, the catalog's internal numbering.
• strength_model and strength_clip - optional overrides. The default is −1, and here's the clever bit: −1 means "keep the catalog's value." Set a real number and it overrides that LoRA's default strength; leave it at −1 and the catalog's recommendation stands.

Outputs: lora_id (int), lora_name (string), and lora_config - the full JSON card.

How it works

The dropdowns are populated from a bundled JSON file (data/loras.json) that ships with the pack. If you've picked a name, it looks up the matching entry; if the name is "unset," it falls back to matching by ID. It then applies your strength overrides (only where you set them), serializes the card, and hands it out. The lora_config you get includes the file's download config, so it's a self-contained "this LoRA, from this location, at this strength" recipe.

The thing you need to understand

This catalog is the author's. The dropdown contains the LoRAs Inoland's own pipeline knows about - things like KarlaKushV5 - with their download files hosted on the author's infrastructure. It is not a list of the LoRAs in your models/loras folder, and it won't include anything you've installed yourself. If your LoRA isn't in the catalog, this node can't see it. That's the single most important fact to grasp, because it's easy to assume a dropdown labeled "lora_name" reads your local files. It doesn't.

So: use this when you're building the pack's config-driven sampler pipelines and the LoRA you want is in the catalog (or you'll add it to the catalog JSON). For your own LoRAs, either add them to data/loras.json (it's a plain JSON file - backup first) or use the pack's direct LoRA loading nodes instead.

Where it fits

Feed lora_config into the sampler-loading chain - the same consumers that Ino Create Lora Config feeds. Because the card carries the file's download config, the pipeline can even fetch the LoRA at runtime via the download dispatcher, then load it.

Gotchas

The −1-override convention is easy to misread: if you genuinely want strength 0 (effectively disabling), −1 as the "unset" sentinel means you can't use −1 as a real strength, and values are clamped to the −1..1 range. And as ever in this pack: enabled off returns empty outputs, and the catalog is read at node load time - edit data/loras.json and refresh ComfyUI to see changes.

Installation

Part of ComfyUI-InoNodes:

• ComfyUI Manager: search "ComfyUI Ino Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/nobandegani/comfyui_ino_nodes && cd comfyui_ino_nodes && pip install -r requirements.txt, restart.

Python 3.10+, ComfyUI 0.18.1+ (V3 schema). No models at install; downloading from the catalog at runtime is where disk and any host credentials come in.