Nodes/ComfyUI-Practical-Tools/Cond Pair Passthrough
ComfyUI Node

Cond Pair Passthrough

Two conditioning wires that travel as a pair

By wenchengxiang·Created 2 months ago·Updated 9 days ago· 3
Cond Pair Passthrough
  • conditioning
  • conditioning_
  • conditioning
  • conditioning

Most conditioning nodes in ComfyUI take one CONDITIONING in and hand one back. This one takes two. Cond Pair Passthrough is the pack's "positive and negative, together" node - two CONDITIONING inputs, two CONDITIONING outputs, nothing changed in between. You'd reach for it when a workflow keeps the prompt pair as a unit: fan your positive and negative encodings into the two inputs, and any downstream node that wants both gets them from one tidy pair of sockets instead of two loose wires crossing the graph.

It exists because a few nodes in this very pack - and a bunch of conditioning utilities across the ecosystem - treat positive and negative as a matched pair. Bundling them through one node keeps the pairing legible: you can see at a glance that this pair is the one feeding your refiner, or the one your conditioning rebalance node is chewing on. The mechanism is the honest kind: the source literally returns the two inputs untouched.

Here's the quirk you'll actually trip over: both sockets are named conditioning in the UI. That's deliberate - the author forced it so the front-end renders two identical, side-by-side conditioning ports (the second input's key secretly has a trailing underscore so ComfyUI doesn't collapse them). The inputs are conditioning and conditioning_ in the schema; both display as "conditioning." That means order is the only way to tell them apart, so wire carefully and don't expect the port labels to help you.

Inputs and outputs that matter

  • conditioning (in, top) - usually your positive.
  • conditioning (in, bottom) - usually your negative.
  • conditioning (out ×2) - same two objects, same order, both labeled conditioning.

If you only connect one side, the other output comes out as nothing, so partial wiring won't hard-crash - it just means one output is empty.

Installing it

Standard for this pack. ComfyUI Manager → Custom Nodes Manager → search "ComfyUI-Practical-Tools" → Install → restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/wenchengxiang/ComfyUI-Practical-Tools

then restart ComfyUI. No pip dependencies, no model files - the whole pack is pure Python on ComfyUI's bundled stack.

Issues and gotchas

Beyond the identical-labels trap, the honest advice is the same as for any passthrough: it doesn't transform anything, so it's only as useful as the graph around it. If you're just moving one conditioning wire, the single-socket Conditioning Passthrough or a core Reroute is less confusing. This node pays for itself when you're deliberately keeping pos/neg paired for a conditioning-utility node - at that point, two clearly-paired sockets beat two orphan wires, identical names and all.

CategoryPractical-Tools/Passthrough

Inputs (2)

NameTypeDefaultDescription
conditioningoptCONDITIONING—
conditioning_optCONDITIONING—

Outputs (2)

NameTypeDescription
conditioningCONDITIONING—
conditioningCONDITIONING—