MultiPreview Auto

MultiPreview Auto: just show me the newest one

MultiPreview is the branch-monitoring node from the comfyUI-multi-preview pack; MultiPreview Auto is its impatient sibling. Same 32 dynamic image inputs, same live-update machinery, but none of the manual controls - no pin buttons, no auto_latest toggle to flip, because "follow the newest" is the only mode it has. If you want to sit back and watch a parallel workflow finish branches without touching anything, this is the one you reach for.

Under the hood it's barely a separate node at all. In the source it's a subclass of MultiPreview that simply never creates the pin-button widgets - the Python class is a handful of lines, and everything else (per-branch receiver injection, preview the instant a branch completes, per-pin batch positions, session preview restore) is inherited wholesale. All the cleverness that makes the parent work applies here unchanged.

Inputs are exactly the same deal:

• image1 … image32 - optional IMAGE inputs. Wire the branches you're monitoring; new inputs appear as you connect them.

There are no outputs - it's a terminal preview node, so it belongs at the end of a branch, not in the middle of one.

When is this actually the right tool? When you're babysitting a long run and only care about whether the newest result looks sane. Seed sweeps, upscaler comparisons, a batch where the interesting output could land on any branch. It's also the tidier choice if you want a compact always-on preview in a corner of the canvas: no buttons, no state to fumble, just a picture that tracks the latest result.

The honest trade-off is that you give up going back. The parent's pin buttons let you flip to an earlier branch or re-view a result that arrived three runs ago; Auto forgets the moment the next input lands. If you're iterating and comparing, that's a real loss. Use Auto when you're monitoring, use the parent when you're deciding. Both nodes arrive together - one install gets you both, so there's no reason not to have them side by side.

Install is the same as the parent, because it's the same pack:

cd ComfyUI/custom_nodes
git clone https://github.com/palealloy2999-prog/comfyUI-multi-preview

Restart ComfyUI and hard-refresh the browser, or find "comfyUI-multi-preview" in ComfyUI Manager. No dependencies, no model downloads, MIT licensed.

Same gotchas apply since it's the same engine: previews are session-only and live in ComfyUI's temp directory, so don't rely on Auto for anything you want to keep, and if it shows nothing after an update, hard-refresh before you start debugging. And remember it's an output node - what you're looking at is a preview, not a saved file.