Fooocus PipeOut

The whole pack runs on one fat wire: a PIPE_LINE that carries your model, clip, vae, conditioning and latent in a single connection. It's convenient until it isn't. The moment you want to hand the pack's model to a standard ComfyUI node - a different sampler, a ControlNet you prefer, a normal VAE decode - you need this node. Fooocus PipeOut unpacks the pipe into its individual parts so you can work with them the ordinary way.

What it does

One pipe in, six named outputs out, each a standard ComfyUI type:

• pipe - the pipe itself, passed through so you can continue the pack's flow and tap the parts.
• model (MODEL)
• pos (CONDITIONING) - the positive conditioning.
• neg (CONDITIONING) - the negative.
• latent (LATENT)
• vae (VAE)
• switch (FLOAT) - this one's a bit unusual: it exposes the refiner switch value (the fraction of sampling before the refiner kicks in, from the Loader). Most of the time you ignore it; it's there so you can wire the switch into nodes that respect it.

There are no parameters. One input, seven outputs, zero settings. If you know what a pipe is, you know what this does; if you don't, read on.

Installing

Standard pack install - ComfyUI Manager, search "Fooocus Nodes", or clone the repo into custom_nodes and restart. No model downloads, no dependencies beyond the pack itself.

When you'll actually reach for it

The canonical case is the ControlNet hybrid: build the Fooocus pipeline through the PreKSampler for that tuned SDXL look, then PipeOut the model and latent into a standard sampler so you can apply a ControlNet the pack doesn't ship. The reverse also happens - people PipeOut and re-pipe when they want the pack's detailerFix on an image that came from outside the pack.

The gotcha

PipeOut is the pack's de-facto "are you sure you know what a pipe carries?" node. If you wire its pos and neg into a standard KSampler and get garbage, check that you're using the conditioning outputs and not the model wire - the classic mistake is grabbing model when you meant pos. And one structural note: the pipe is the pack's internal convention, so outputs from this node only interact cleanly with other Fooocus nodes if you keep using the pass-through pipe. Break the chain deliberately, not by accident.