🔹ClipPass

ClipPass takes a CLIP and hands you back the exact same CLIP. The entire implementation is return (clip,) - there is nothing under the hood. So the honest first answer to "what does it do?" is: nothing. The useful question is why it's there.

Why a no-op ships in this pack

These pass-through nodes exist to keep the author's own workflows readable. The comfyui-photoshop pack is mostly Photoshop plumbing - canvas in, render out, websocket chatter - and in a graph like that, a CLIP cable stretched across the whole canvas is a mess. ClipPass gives you a stable anchor: break the long wire at the pass node, reroute, and you never have to trace which sampler the CLIP was feeding.

It's also handy as a waypoint in live workflows. The pack's real-time loop means you're rearranging and re-running constantly; a pass node is a cheap, safe place to cut or reconnect without touching your sampler settings. And in a graph full of "🔹" nodes, it doubles as a label - a tidy spot to eyeball that the right CLIP is flowing through.

Using it

One input, one output, both type CLIP:

• clip (CLIP) in → clip (CLIP) out.

That's the whole interface. Wire whatever you'd normally wire into your text encoder or conditioning, and the pass node sits between them. If the output doesn't match what you expected, the problem isn't the node - it's upstream of it.

Installing it

It comes with the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/NimaNzrii/comfyui-photoshop

or ComfyUI Manager → search comfyui-photoshop → install → restart.

Honestly? If you never touch this node, you're not missing anything. It's a convenience for layout, not a feature. But now you know what it is instead of wondering why there's a do-nothing CLIP node staring at you in the bundled workflows.