Nodes/comfyui-model-manager-nodes/Merge LoRA Info (Model Manager)
ComfyUI Node

Merge LoRA Info (Model Manager)

Combine up to four LoRA info lists into one

By blackpaw-studio·Created 7 months ago·Updated 7 months ago· 0
Merge LoRA Info (Model Manager)
  • lora_info_1
  • lora_info_2
  • lora_info_3
  • lora_info_4
  • lora_info

Most nodes in this pack move models around. Merge LoRA Info (Model Manager) moves data: it takes up to four MM_LORA_INFO lists and concatenates them into one. It doesn't touch a model, doesn't hit the network, doesn't download anything. It's plumbing, in the purest sense - and it exists because the pack's LoRA loaders track what you applied, and sometimes you need all of that history in one place.

The mechanism

Every Model Manager LoRA loader emits an lora_info output: a small list of records describing each LoRA that was applied - its model ID, version, name, and strength. When you stack LoRAs across separate loader nodes in one workflow, you end up with several of these lists scattered across the graph. This node merges them:

  • Four optional inputs: lora_info_1 through lora_info_4, all type MM_LORA_INFO. Wire in only the ones you're using - empty inputs are simply skipped.
  • One output: lora_info, a single combined list, in the order you connected them.

That's the whole thing. The ordering matters if downstream code cares about application order (LoRAs are applied sequentially, so order is part of the story), so wire them in the order they're applied.

When it's actually useful

The honest answer: you'll reach for this when something downstream wants the complete LoRA picture. The obvious consumer is Upload Image (Model Manager), which stamps the generation's metadata - including its LoRA list - onto every image it uploads back to the server. If your workflow applies LoRAs through two separate Model Manager loaders, merging their lora_info outputs into the upload node records the full stack instead of just one branch. It's also handy for a Show Text-style inspection node if you want to eyeball what got applied.

If you never upload images and never inspect metadata, skip this node. It earns its place by being boring and correct, not by being exciting.

Install

The usual: ComfyUI Manager (search comfyui-model-manager-nodes) or clone + pip install -r requirements.txt:

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 ComfyUI. No connection, no API key, no models - this node works the moment it's installed, since it only passes data through.

Gotchas

  • Inputs that receive nothing produce an empty list, not an error. A merge with no connections returns an empty list, which is fine for the upload node but can be confusing if you're inspecting output and see [].
  • Order is preservation, not sorting. Connect lora_info_1 first and lora_info_2 second and that's the order you get out.
  • If you're merging lists from non-Model-Manager LoRA loaders, the types won't match - this node only understands the pack's own MM_LORA_INFO type.

Simple, deterministic, no surprises. When you need the full LoRA ledger in one wire, this is the node.

Categoryloaders/model-manager

Inputs (4)

NameTypeDefaultDescription
lora_info_1optMM_LORA_INFO
lora_info_2optMM_LORA_INFO
lora_info_3optMM_LORA_INFO
lora_info_4optMM_LORA_INFO

Outputs (1)

NameTypeDescription
lora_infoMM_LORA_INFO