CLIP Passthrough

CLIP Passthrough does exactly one thing: takes a CLIP model in through its clip input and hands the identical object out its clip output. It's a wire extension in node form, and it exists because the CLIP wire is one of the longest, most tangled lines in any workflow.

Think about what a CLIP wire has to cross. It leaves the checkpoint or CLIP loader and has to reach every CLIP Text Encode in the graph - the positive, the negative, and any per-region encodes you've stacked. That's a line that runs the full width of the canvas and gets dragged around every time you reorganize. The plumbing-layer docs are blunt about this: a big chunk of ComfyUI maintenance is just fighting "messy noodles," and these nodes exist to fight illegibility.

How it works

One optional CLIP input, one CLIP output, value passed through unchanged - the same pass-through mechanics as every node in this pack. Because the input is optional, an unwired CLIP Passthrough emits None, which matters here more than for a bool: most downstream nodes that consume CLIP will throw if you feed them nothing, so keep the wire present.

Where you'd use it

• Subgraph boundaries. When you collapse a region into a subgraph, the passthrough becomes the explicit "this subgraph needs a CLIP" port at the edge. Clear to read, easy to wire.
• Turning corners. A single passthrough lets a wire zig where it needs to instead of streaking across the whole canvas, same idea as a reroute but with a typed, labeled socket.
• One source, many consumers. Fan the CLIP out to a half-dozen encodes from a single node instead of pulling from the loader each time.

If your real goal is consolidating the two encodes themselves, note this pack also ships a Dual CLIP Text Encode node that encodes positive and negative with one shared CLIP - the passthrough is for routing, that node is for collapsing.

Install

ComfyUI Manager → search "Tojioo Passthrough" → install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Tojioo/tojioo_passthrough.git

Restart ComfyUI. Zero heavy dependencies and no model downloads - the pack is a lean collection of Python nodes with a bundled frontend, and it's on the Comfy Registry under publisher tojioo.

Common issues

An unwired CLIP Passthrough returns None, and that's the failure you'll actually see: a red error downstream from a node that "looks" connected because the passthrough is in the path. The fix is wiring the passthrough's input, not the node after it. And if you bypass or mute the loader feeding it, the passthrough passes that "missing" state through rather than inventing a CLIP - which is by design, but worth knowing when a branch silently drops out.