IO Pipe 36CH Any

This is the one you reach for when twelve channels are too few, twenty-four are almost enough, and you want to stop counting. Pipe 36CH Any carries thirty-six any-type values on a single wire - plus the pipe context for chaining - and it's the top of the pack's pipe food chain: 12, 24, 36, take your pick. If you're building a module that needs to hoard a lot of state - a reusable video pipeline that shuttles image, mask, audio, conditioning, prompt fragments, sampler settings, resolution, metadata, and a few things you haven't decided on yet - this is the fat cable tray for it.

Let me save you a decision: start with the 12. The pipe pattern's whole reason for existing is to make a graph legible by bundling values down one wire, and the plumbing docs' warning applies in spades here - the more a bundle carries, the more it hides. A 36-socket node is a wall of pins, and every value inside is invisible until you unpack it. The 36 exists for genuinely fat interfaces and for the workflow author who's building something modular enough to warrant a fixed, wide contract. It is not a reward for being disorganized.

How it works

Mechanically identical to the 12 and 24 versions - same context-utility code, bigger channel map. Every any_N input is optional and typed *; unconnected channels become None. The pipe input chains: start from an existing bundle, override only the channels you feed, carry the rest forward. All 36 outputs mirror their inputs plus the pipe output.

The chaining behavior is the part to lean on. A 36-channel pipe threaded through a long workflow is unwieldy, so the pattern is usually: assemble the bundle once, pass it through a few modules that each touch their own channels via Pipe IO style nodes, and unpack at the end. If you're feeding every channel every step of the way, you're doing pipes wrong - you should be touching the channels you own and letting the rest ride.

The inputs that matter

• pipe - the bundle you're extending. This is the one that makes a 36-channel pipe usable at all.
• any1…any36 - the channels. Feed the ones you own; leave the rest to ride through from the incoming pipe.

Install

Part of ComfyUI_Eclipse (r-vage). ComfyUI Manager, search ComfyUI_Eclipse, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart ComfyUI. No models, no heavy deps beyond the pack's standard stack. And the standing warning for shared workflows: the pack's v4.0 removed legacy node IDs after the RvTools_v2 rename, so a workflow that won't load usually needs the built-in Workflow Migration Tool, not a reinstall.

Common issues

The big one is self-inflicted: 36 channels is a lot of places to lose a value, and the opaque-bundle debugging tax grows with the channel count. If a downstream value is None, it's almost always an unconnected channel or a pipe that was assembled before the value existed (stale context). Practical rules: keep the bundle contract documented (name the channels in the node title or a note), unpack with a Show Any when you're lost, and don't chain 36 channels through ten nodes - assemble early, touch what you own, unpack late.