Prompt Distributor

You've got eight prompt variations you want to compare, and you're doing the thing everyone does: paste variation one into the KSampler, queue, wait, paste variation two, queue, wait. Somewhere around variation four you start plotting your escape from ComfyUI. Prompt Distributor is the pack's answer to that ritual. Feed it the whole list once, and it fans the prompts out into up to ten ordered slots that each take their own branch of the graph - then the rest of the run is one queue entry and zero copy-pasting.

This node is the head of the parallel-testing pipeline in the ComfyUI Orchestration Toolkit, a young pack (first public release September 2026, one author org called Flows & Frames) whose hub node is PromptOrchestrator. That hub is what produces the prompt list in the first place; Distributor is what turns the list into branches.

How it works

Distributor doesn't generate anything. It's a routing node in the classic plumbing sense: it takes your two prompt lists and packs them into a single custom object called a Prompt Manifest (ORCHESTRATION_PROMPT_MANIFEST). Think of the manifest as a versioned routing table - ten slots, each either active with a positive/negative pair or inactive and empty. Everything downstream reads from that one object, which is why the whole chain stays consistent without ten loose wires.

Two honest notes on the "parallel" word, because the README leads with speed. The branches are genuinely independent - you can hang a different model, sampler, or even a different API node off each one, which is the README's "route to different APIs" use case. But ComfyUI's normal executor still works through a graph node by node, so if all ten branches run the same sampler on the same GPU, don't expect ten renders at once. The win is structural: one pass tests the whole list, each branch can be wired differently, and you never touch the prompt widgets between runs.

The inputs and outputs that matter

• positive_prompts and negative_prompts - connect both to the Positive Prompt and Negative Prompt outputs of a PromptOrchestrator. They must have the same number of items (in positive-only mode the negatives are just empty strings, which is fine).
• branches (INT, default 4, 1–10) - how many parallel branches should be active this run. This is the knob you'll actually touch.

Output is exactly one Prompt Manifest wire. Feed it to each Prompt Slot Picker in your branches and to the Prompt Collector at the far end - they all need to be reading the same manifest.

Common issues

The biggest gotcha is the silent truncation. If your list has more prompts than the branches count, the extras don't error out - they're just dropped, and the only trace is a warning line in the console telling you prompts N to M were ignored. If a branch "isn't running," check that first: either raise branches or trim the list. Mismatched list lengths between positives and negatives, or an item that's empty in both, will hard-error instead, which is the correct behavior - you want that loud.

Installation

Same for every node in this pack - one install gets you all of them (PromptOrchestrator, Distributor, Slot Picker, Collector, Image Picker, Save String, plus a Node State Controller), under the prompt_orchestration category.

Via ComfyUI Manager: Install Custom Nodes → Search → "Orchestration Toolkit" (publisher flows-and-frames), install, restart. Or the manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/flows-and-frames/ComfyUI-Orchestration-Toolkit.git

Then restart ComfyUI. There's no requirements.txt and no model download - the pack is pure Python plus a bit of frontend JS and only needs Python 3.10+. Because it's brand new with essentially no community history yet, treat any quirk you hit as fresh ground: the GitHub issues tab is where the real answers will accumulate over the next few months.