MixMod Pipeline

MixMod Pipeline is the pack's organizational node, and honestly it's the least exciting one in the set - which is fine, because it exists to keep the rest of the graph from turning into spaghetti. You wire a model plus its positive and negative conditionings into it once, and it hands you a single PIPELINE bundle you can route anywhere.

The use case is obvious the moment your mix grows past two models. Without a pipeline you're dragging the same checkpoint, same CLIP-encoded positive, same negative into every MixMod Guider Component node you add. With it, you change the prompt or swap the checkpoint in one place and every component that consumes the pipeline picks it up. It's a rename-able preset for "this model, told this thing."

Inputs and output

Everything is required: model (any checkpoint the pack supports - SD1.5, SDXL, Pixart Sigma), positive, and negative. No weights, no CFG, no options; those live on the consumer nodes, not here. The single output is a PIPELINE that feeds the MixMod Guider Component Pipeline node, which unpacks it into an actual mix component with weight and CFG applied.

That's the whole job. It's a data-holder - under the hood it just stores {model, positive, negative} in a dict and passes it on. Nothing is executed or blended at this node; all the work happens later in the guider.

Installing and practical notes

It's part of the ComfyUI-MixMod pack (Kantsche's model-mixing suite, announced on r/StableDiffusion in mid-2025 as "A new way of mixing models"). Install via ComfyUI Manager by searching "ComfyUI-MixMod", or:

cd ComfyUI/custom_nodes
git clone https://github.com/kantsche/ComfyUI-MixMod

then restart. No requirements.txt, no model files to fetch - this pack rides on plain torch and ComfyUI's samplers. Companion packs (ComfyUI-GGUF + ComfyUI_ExtraModels for Pixart Sigma mixing) are only needed if you actually mix those models.

The one thing worth keeping in mind: a PIPELINE is just a snapshot, not a live reference. If you change the checkpoint after building the graph, the components downstream re-evaluate from the new input, so nothing stale persists. And since the whole pack holds every mixed model in VRAM for the entire sampling pass, a pipeline doesn't make the mix any cheaper - it just makes it tidier. Given how fast these graphs sprawl once you chain three components, tidier is worth something.