Detailer Pipe Passer

If you've ever used Impact Pack's FaceDetailer or Detailer (SEGS), you've met the detailer pipe: a bundle that carries model, clip, vae, positive and negative conditioning down one wire. It's great for the graph, but the moment you want to branch that bundle - run the same detailer pipe into two different detail passes, or swap between a low-denoise and high-denoise setup - you're dragging thick wires across the whole canvas. The Detailer Pipe Passer is the router that keeps that tidy.

What it is

A typed passthrough for the DETAILER_PIPE data type. In goes a detailer pipe, out comes the identical pipe, nothing modified. The point is a stable, labeled spot where a pipe can be split or switched, the same trick as the pack's Conditioning, Model, and Float passers but for the impact-style pipe bundle.

The typing matters here more than for most passers. A detailer pipe is a structured object - it's easy to lose track of which pipe variant you're holding - so having a socket that declares DETAILER_PIPE on both ends means ComfyUI will refuse to silently connect a wrong-shaped pipe into your detailer. That's a failure you want at connect-time, not render-time.

How it works

execute returns the pipe input untouched. The input tooltip says exactly that: "Detailer pipe input to be passed through." Because it's a reference pass, nothing downstream is duplicated - the same pipe object continues through the graph, and any node that pulls values off it sees the current state of the bundle.

Where you'll actually use it: feeding one Detailer (SEGS/pipe) node from two alternative sources, or running a single detailer pipe into multiple detail passes while keeping the graph readable. Mute or bypass the passer to disable a branch instead of yanking wires.

Wiring

One input (pipe), one output (pipe), no widgets. If you want to change what's inside the pipe - a different model, a higher denoise - do that at the nodes that build or modify it, not here. This node only moves it.

Install

It's part of ComfyUI_Eclipse (formerly RvTools, rewritten and renamed in v4.0.0). Via Manager: search ComfyUI_Eclipse, install, restart. Or:

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

Restart and it's under Eclipse → Router → Typed. Note that the pack vendors its own copy of Impact Pack's detailer machinery (extern/impact), so you don't need Impact Pack installed for the Eclipse detailer nodes - one less thing to break.

Troubleshooting

• "Not a valid detailer pipe" type error: you've fed it a plain PIPE or a context pipe instead of a DETAILER_PIPE. Check what the upstream node actually emits - Eclipse's context pipes are a different type from the detailer pipe.
• Detail pass ignores the passer: it can't; it's a passthrough. Inspect the nodes upstream that build the pipe for the settings you expect.
• Node missing: restart ComfyUI and check the console for import errors; old RvTools-era workflows may need the Workflow Migration Tool to load cleanly.