🔗 Pipe 10CH Any

The 🔗 Pipe 10CH Any is the mid-size rung of the pack's fixed-channel pipe ladder: one pipe in/out plus 10 any channels that carry anything. It's the sweet spot for a workflow with a real bundle of signals - a few models, a conditioning or two, a latent, some metadata strings - where 5 channels are tight and 20 is overkill.

How it works

Identical mechanics to its siblings (5, 20, 30, 40-channel): every channel is a * wildcard type, so IMAGE, LATENT, MODEL, MASK, CONDITIONING, STRING and the rest all flow through without type checking. You inject values into any1…any10, pass the bundle through pipe, and pull the same channels out of a matching Pipe node downstream. Unconnected channels inherit the upstream pipe's value, which is what lets you chain pipes end to end and add one new signal anywhere in the middle without rewiring everything after it.

The implementation follows the rgthree context-utils pattern the pack's pipe code is derived from, which keeps it interoperable with similar context-style nodes and easy to reason about: the pipe is just a dict-like bundle, the channels are its keys.

Inputs and outputs

• pipe (optional in/out) - the bundle you're extending or forwarding.
• any1 … any10 (optional) - values to stuff in; each mirrors to its matching output.

When to pick this size

If your bundle is "a handful of settings plus a couple of big objects," 10 channels gives you room to grow without a wall of empty ports. If you're designing a reusable template where the port count must stay fixed and predictable, these static nodes beat the dynamically-growing Pipe Hub. If you truly only carry four or five things, take the 5CH version - a 10-channel node with six unused ports is just clutter, and empty channels pass None downstream if you ever read them by mistake.

Install

Ships in Light-x02 Nodes - ComfyUI Manager → search "ComfyUI-Lightx02-Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/Light-x02/ComfyUI-Lightx02-Nodes

Restart ComfyUI, find it under 💡Lightx02/Pipes. No extra dependencies or downloads. As with the rest of the pack, uninstall any older standalone Light-x02 node repos first to avoid duplicate-registration errors.