Flake Combo

Flake Combo is the batch node hiding inside a familiar face. Look at its inputs and outputs and it's identical to Flake Stack - model_family, flake_data, flakes_json in, one updated flake_data pin out. The backend genuinely is the same code; Flake Combo is literally a subclass of FlakeStack. What makes it different is the frontend, and the difference matters: where Flake Stack lets you stack many flakes at once, Flake Combo enforces one active flake at a time, and when you hit Queue it walks every combination across all FlakeCombo and FlakeModelCombo nodes in your graph and queues them all.

That's the whole pitch, and it's a good one. You get the classic grid UI with the add / load / reorder / edit / bypass controls, but now it's a tool for systematic sweeps. Want the same character in three outfits, two moods, and a handful of poses? Put each outfit, mood, and pose in its own Flake Combo, and the pack generates every combination for you, each with the correct prompt fragments and LoRAs merged. The node shows a live Jobs: N counter and highlights the active combination while it runs, so you can watch it chew through the grid instead of babysitting the queue.

The "one flake per combo" rule is the design constraint that makes the combinations tractable - with a stack you'd get one merged monster prompt, not a product of choices. If you want to keep a base layer constant across every combination (say, the character itself), you don't stack it into the combo; you leave it in an upstream Flake Stack or in the model preset, and only put the axes of variation into combos. That split - invariant stuff upstream, varying stuff in combos - is the mental model that makes this node sing.

Gotchas that are real. A combo that iterates four positions across five styles is twenty jobs, not one. Budget accordingly before you click queue - the Jobs: N counter is there to stop you from discovering it the hard way. Bypassed flakes are excluded from the queue, so use the toggle rather than deleting things you might want back. And remember the file-format rules from the rest of the pack: flake paths must resolve under models/flakes/ and models/loras/, and ControlNet images go in ComfyUI/input/.

Install. ComfyUI Manager → search ComfyUI Flakes → Install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/JeyzerMC/comfyui-flakes

then restart. PyYAML is the only dependency and it's already part of ComfyUI core.

The pack is young and this is the node that sells it - if you've ever sat there clicking Queue over a matrix of prompts, Flake Combo is the reason to install it. It's also brand new, so expect rough edges; the combo queueing logic lives in the frontend and is exactly the kind of thing that can break when ComfyUI's UI changes underneath it.