Multi-Pipe Out

Multi-Pipe Out is the other half of the bundle. Where Multi-Pipe In gathers a dozen values into one XE_MULTI_PIPE wire, this node takes that single wire and fans it back out into individual outputs - up to 50 of them, slot00 through slot49, each a wildcard (*) that passes whatever came in. If the In node is a zip file, this is the unzip.

It's a deliberately boring node, and that's the point. You don't configure it, you don't set types, you connect a pipe and the outputs fill themselves in. The one genuinely clever bit is the dynamic sync: because the frontend knows which Multi-Pipe In you're connected to, the Out node's output names mirror the slots you actually populated on the In side. Wire up a pipe that carried model, clip, vae, and seed, and this node presents those named outputs instead of a wall of slotNN labels you have to count.

The inputs and outputs:

• pipe - a single XE_MULTI_PIPE input, the bundle you want unpacked.
• slot00 … slot49 - the unpacked values. Every one is type-agnostic, so an image comes out an image, a latent a latent, and anything that wasn't in the bundle comes out None.

That None behavior matters more than it looks. ComfyUI reads an unwired optional input as None, so a pipe that doesn't carry a value behaves exactly like a node you never connected - downstream fallback logic (like a first-non-null switch) just skips it. You get "this branch isn't active" for free, no muted nodes required.

Where you'd actually use it: on the far side of a bus. Build a big workflow where Multi-Pipe In collects the shared values at the top, run one fat wire down the middle of the graph, then drop a Multi-Pipe Out wherever a cluster of nodes needs its own copies. It's the classic context-bus pattern the KB's node-plumbing doc calls the single most important design in the plumbing layer - with the same warning attached: the bundle hides which version of each value is inside. If you unpack clip from a pipe assembled before a LoRA node ran, you silently use the pre-LoRA clip. The one wire that made the graph legible also hid what changed. When you're actively iterating on a section, pull values onto explicit wires so you can see them.

The other honest limitation is lock-in. XE_MULTI_PIPE is this pack's own type, so an In from another pipe system (rgthree Context, Efficiency's pipes) won't plug into this Out. Decide once which bus your graph speaks, and don't mix.

Install is the standard pack routine - ComfyUI Manager, search "ComfyUI-XENodes", or clone it in:

cd ComfyUI/custom_nodes
git clone https://github.com/xeinherjer-dev/ComfyUI-XENodes.git xenodes

then restart ComfyUI. Nothing to download, no model files, no pip step for this node. If it doesn't appear, check the ComfyUI console rather than assuming the install failed - the pack imports all its node modules together, so a sibling node's missing dependency (SaveAudio needs PyAV's av) can prevent the whole menu from loading.

One quirk worth knowing: the output-name sync is a frontend behavior, so it depends on the pipe being actually connected in the loaded graph. Reconnect the pipe wire if the names ever look stale after opening an old workflow - the sync re-runs on connection, not on file load.