Conditioning In, Conditioning Out

This is about as simple as a node gets: conditioning goes in, the same conditioning comes out. It doesn't change anything about the conditioning itself. So why does it exist? Because a passthrough node is a genuinely useful piece of graph plumbing. It gives you a fixed, named point in the wire that you can reroute, label, and reorganize around - the kind of thing that keeps a big workflow from turning into an unreadable tangle.

If you've built anything complicated in ComfyUI, you know the pain: you want to redirect where your positive conditioning goes, or insert a clean junction so you can swap what's downstream without re-dragging five wires. A typed passthrough is the tidy way to do that. It's not a creative tool and it won't show up in anyone's "top nodes" list, but as connective tissue in a large graph it earns its keep.

How it works

There's no mechanism to speak of - it receives a CONDITIONING and returns it unchanged. Think of it as a labeled waypoint on the conditioning wire. Its value is organizational: a stable anchor you can route through, a spot to break and rejoin a connection cleanly, a node you can bypass or reroute as a single unit while everything hanging off it stays put.

The inputs and outputs that matter

• conditioning - the CONDITIONING coming in (typically the output of a CLIP Text Encode or another conditioning node).

The output is a single CONDITIONING - the same thing, passed through, into your KSampler or the next conditioning node.

How to install it

ComfyUI Manager, search JNodes, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/JaredTherriault/ComfyUI-JNodes
pip install -r ComfyUI-JNodes/requirements.txt

No models involved.

Common issues & troubleshooting

"It's not doing anything." Correct - that's the design. This node does not modify conditioning. If you were expecting it to combine, mask, or set an area, that's a different node; this one only passes through. For actual conditioning ops you want ComfyUI's built-in Conditioning (Combine/Concat/Set Area) nodes or something like the conditioning tools in other packs.

Do I need it? Only if you want a passthrough/reroute point specifically typed to conditioning. If you're just tidying wires, ComfyUI's built-in Reroute node does the generic version. Reach for this when you specifically want a conditioning-typed anchor in the graph.

A wire won't connect through it. The input and output are both CONDITIONING. Anything that isn't conditioning won't attach - make sure what you're feeding in is actually a conditioning output, not a latent or a model.