ComfyUI Node

latent pass

A named socket for your latents

By aegis72·Created 3 years ago·Updated 2 years ago· 39
latent pass
  • latent
  • latent

Latents are the awkward middle state of a diffusion workflow - not an image, not text, just the compressed noise-ish tensor that samplers chew on. The Aegisflow Latent Pass is the passer that moves that state around in modular workflows: a latent in, the same latent out, nothing else.

Why it exists

This is one of the pack's "passer" nodes, and they all share the same two jobs. First, their inputs are optional, which means they don't trigger the auto-wiring behavior where ComfyUI and some custom node packs try to "fix" open required inputs by connecting any matching output - sometimes the wrong one, breaking the graph invisibly. Second, they're nameable targets for Use Everywhere / Anything Everywhere style invisible-broadcast nodes. Rename the passer, point your sender at it, and a latent generated somewhere else in the graph arrives here without a visible wire.

You'll most often see latent passers sitting between a latent source and a KSampler or VAE Decode in workflows where the sampling section is a reusable module. When the module is dropped into a bigger graph, the passer is the plug that keeps its latent socket satisfied - and when you're building the template, it stops ComfyUI from grabbing whatever latent happens to be lying around.

Inputs and outputs

  • latent (LATENT, optional) - passed through unchanged.
  • Output: latent (LATENT).

Empty input means None output, which is fine while a sender is filling it at runtime and a footgun if you wire it empty into a sampler.

Installing it

Same pack, same steps:

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

Restart ComfyUI, or grab "AegisFlow Utility Nodes" from ComfyUI Manager. No models, no heavy deps.

Where people get burned

A latent passer won't generate, resize, or empty a latent - it's pure routing. If you feed it nothing and no sender targets it, downstream gets None, and latent consumers are not graceful about that. Keep it as the mailbox it is: wire something in, or let a Use Everywhere sender do the delivery.

CategoryAegisFlow/passers

Inputs (1)

NameTypeDefaultDescription
latentoptLATENT

Outputs (1)

NameTypeDescription
latentLATENT