Basic Pipe Passer
Carry a BASIC_PIPE through your graph without re-wiring it
- pipe
- pipe
Basic Pipe Passer passes a BASIC_PIPE through unchanged. A basic pipe is ComfyUI's compact data bundle - the small sibling of the big context pipes that carry model, CLIP, VAE, and conditioning down a single wire. This node's entire job is to let that bundle travel around your graph without you having to unpack it and re-route four individual wires.
The pipe idea is worth a beat, because it's the single most important pattern in the plumbing layer: instead of dragging model, clip, vae, positive, negative, latent, and settings as a dozen separate wires across the whole graph, you bundle them into one object that travels down one wire. Eclipse builds a whole ecosystem on this - 12/24/36-channel pipes, context pipes, the Concat Pipe Multi node for merging them. A pipe is just a Python dict with canonical keys, and nodes pull off what they need and push back what they changed.
Why a passer for pipes
Because the bundle is opaque, a pipe passing through a graph needs the same treatment as any other value: a clean place to break a long wire, a named anchor that says "this is the pipe," and a socket that accepts only pipe data so you can't wire the wrong thing into a pipe input by accident. The typed constraint is the real win here - BASIC_PIPE sockets are picky, and a typed passer gives you a safe way to reroute them.
How it works
A MatchType input constrained to the basic pipe type, handed directly to a same-typed output. No unpacking, no merging, no mutation - pipe in, pipe out. The contents (the models and settings inside) are untouched; it's a carrier, not a processor.
Inputs and output
pipe- the basic pipe input to be passed through.- Output -
pipe, the same bundle.
One input, one output, no widgets.
Where you'd use it
- Breaking a long pipe wire into shorter legs so the graph stays readable.
- Serving as an explicit "the pipeline passes here" checkpoint in a large workflow - attach a debug node or just use it as a visual milestone.
- Routing a pipe around a region without dragging it through nodes it doesn't need.
Installing it
Part of ComfyUI_Eclipse, installed once:
cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse
Restart ComfyUI (or ComfyUI Manager β search "ComfyUI Eclipse"). No extra dependencies.
Gotchas
The pack-wide note: ComfyUI_Eclipse was formerly RvTools, and v4.0.0 removed all legacy nodes - old workflows need the Workflow Migration Tool node (or python tools/migrate_workflow.py <workflow.json>) to rewrite old IDs with a backup. And one thing to keep in mind that applies to all pipe bundles: a pipe is only as current as its last update. If you pass a stale pipe through, you'll happily carry stale values - the passer doesn't refresh anything, and that's the debugging tax the whole pipe pattern charges (see the KB's context-bus discussion). Pass the pipe after whatever updates it, not before.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| pipe | COMFY_MATCHTYPE_V3 | Basic pipe input to be passed through. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| pipe | COMFY_MATCHTYPE_V3 | β |