Forward Conditioning

Forward Conditioning is a pass-through node that accepts one CONDITIONING input and returns it untouched. No widgets, no processing - the entire implementation is "give it back." It belongs to a trio of forwarding nodes in this pack (Forward Any, Forward Model, and this one), and its reason to exist is typing.

Conditioning is ComfyUI's bundled "prompt + model context" object that comes out of CLIP Text Encode and goes into the sampler. It's a thick, opaque object, and there's no reroute socket type for it that behaves the way you want in every situation. Dropping a Forward Conditioning node on the wire gives you a stable, named, typed endpoint: pull off a copy of the conditioning at a specific graph position, attach a Show Conditioning debugger, or give the wire a clean handle to reconnect while you reorganize a workflow.

Because it's typed CONDITIONING rather than *, it won't silently accept an image or a latent - you get a proper type-checked connection. If you need that freedom on both sides, Forward Any is the any-type sibling.

The single input is conditioning, the single output is ->, both CONDITIONING. That's the whole schema.

One honest caveat: this does nothing you couldn't do with a well-placed reroute in most workflows. Where it pays off is the same place the other forwarding nodes pay off - when you're building something like a subgraph or a shared template where you want a named, self-documenting socket instead of a bare wire, or when a wire is getting so long that a break point helps you read the graph. Wiring it in changes zero pixels.

Installing it

This ships in ComfyUI-ImmacTools by Immac - MIT-licensed, personal-use, and dependency-free beyond what ComfyUI already has (no model downloads, no pip installs). ComfyUI Manager by repo URL, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Immac/ComfyUI-ImmacTools

Restart ComfyUI afterward. The pack targets the newer ComfyExtension API, so keep ComfyUI updated or the node won't register; it appears under the Example category, so search for "Forward Conditioning" or "Immac".

Common issues

The only failure mode is expecting it to do something. It won't convert, merge, or alter conditioning - for that you want a Conditioning Combine or a text-encode node. And remember that a pass-through doesn't break the execution path: the upstream CLIP Text Encode still runs, it just hands its result through. If your goal was to skip the encode entirely, bypass the whole branch instead.