conditioning pass

The Aegisflow Conditioning Pass is a single-socket passer for CONDITIONING - the baked prompt data that comes out of CLIPTextEncode and goes into a KSampler. One conditioning in, the same conditioning out. That's the whole node, and it earns its place for reasons that have nothing to do with the conditioning itself.

Why it exists

Every node in this pack's "passer" family exists because modular ComfyUI workflows keep getting sabotaged by autowiring: ComfyUI and some common custom nodes try to "fix" open required inputs by connecting any output that matches the type, and conditioning is one of the types where a wrong guess is invisible - your image just comes out looking off, and nothing errors. Because this passer's input is optional, it never invites that fixing. It also works as a nameable target for Use Everywhere / Anything Everywhere invisible-broadcast nodes, so a conditioning generated somewhere else can arrive here by name, with no wire drawn across the graph.

It's the socket you put on a modular sampling section that says "this module wants a CONDITIONING here" - a plug for a half-built template, and a visible anchor for the invisible-wiring system.

Inputs and outputs

• conditioning (CONDITIONING, optional) - passed through unchanged.
• Output: conditioning (CONDITIONING).

No input means a None output. Fine when a sender fills it at runtime; a problem if you wire an empty passer into a sampler.

Installing it

Standard for the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/aegis72/aegisflow_utility_nodes

Restart ComfyUI, or grab "AegisFlow Utility Nodes" from ComfyUI Manager. No model downloads, no extra dependencies beyond what ComfyUI ships.

Where people get burned

It won't encode, merge, or refine conditioning - that's all upstream. And respect the empty-socket rule: nothing in and no sender means nothing out. If you find yourself needing positive and negative at once, the pack's "posneg pass" carries both; this one is for the single-socket case.