CondPassThrough

CondPassThrough takes your positive and negative CONDITIONING and hands them straight back out, unmodified. Like its sibling ModelPassThrough, it exists for exactly one reason: to work around Set nodes not supporting bypass cleanly, and it bundles both conditioning wires into a single node instead of making you insert two separate pass-through nodes.

Why this exists

KJNodes' Set/Get system lets you tag an output by name and pull it back in anywhere else in the graph, which is a genuinely nice way to tame a large workflow's wiring. The catch is that a Set node can't be bypassed transparently - if you're used to bypassing nodes to A/B a change without deleting anything, bypassing a Set node directly won't let your data flow through the way you'd expect.

Positive and negative conditioning almost always travel together - they come from a matched pair of text encodes, they feed a matched pair of Set nodes, and they get pulled back together downstream into the same sampler. Rather than needing two generic single-type pass-through nodes side by side, CondPassThrough covers both in one: drop it in front of your positive/negative Set nodes, and now there's a single bypassable link in the chain instead of two.

The inputs and outputs that matter

• positive (CONDITIONING, optional) in → positive (CONDITIONING) out, unchanged.
• negative (CONDITIONING, optional) in → negative (CONDITIONING) out, unchanged.

Both are optional on the input side, so you can use the node for just one of the pair if that's all your graph needs at that point - you're not forced to wire both if only one is relevant.

Installing it

Ships with the pack:

• ComfyUI Manager - search KJNodes for ComfyUI, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/kijai/ComfyUI-KJNodes, then pip install -r ComfyUI-KJNodes/requirements.txt, restart.

Zero overhead - no models, no meaningful dependency footprint. It's a plumbing node.

Common issues & troubleshooting

"This node doesn't seem to do anything." Correct, by design - see above. If your workflow doesn't use KJNodes' Set/Get system, there's no reason to reach for this node; a plain wire from your conditioning encode to wherever it's needed does the same job with one less node in the graph.

I bypassed my Set node and lost my conditioning. That's the exact problem this node is built to prevent. Put CondPassThrough in the chain right before the Set node(s), and bypass this node instead of the Set node when you want to A/B disable the step.

Only need this for the model, not conditioning. Check out ModelPassThrough - same idea, same reason to exist, just for a MODEL wire instead of a conditioning pair.