WAN Model Passer

WAN Model Passer is the sibling of the pack's other typed passers, and it does exactly what the name says: takes a WAN video model in one socket and hands it out the other, unchanged. No sampling, no patching, no cleverness. If you've read the VAE Passer article you already know the pitch - this is the same trick for the WANVIDEOMODEL type specifically.

Why it exists

WAN video pipelines are the most wire-dense workflows most people will build. A single WAN model output often has to reach a sampler, a context node, an optional re-encoder, and a preview branch - and if you're running one of the loop-based Eclipse WAN workflows, the model gets threaded through multiple subgraph boundaries. Raw wires across a big canvas turn into an unreadable mess, and that's where a typed passer earns its keep: it gives you a clean anchor point near each consumer so the graph reads left-to-right instead of looking like a plate of spaghetti.

The "typed" part matters more than you'd think. A generic * (ANY) passer will happily accept anything, which is flexible and also how you accidentally route a CLIP into a slot expecting a video model. This node declares the WAN video model type on both sides, so ComfyUI's type checking catches that kind of mistake before you waste a generation on it. It's a wire with a guardrail.

Inputs and outputs

One input, model - connect your WAN video model, however you loaded it (ComfyUI's own WAN loader or the companion ComfyUI_SmartModelLoader pack both produce the type this passer expects). One output, model, with the same value. Nothing to configure, nothing to break. The entire value proposition is that you can't get it wrong, which is more than most ComfyUI nodes can claim.

When to bother

Honestly, if you're running a minimal WAN workflow - model → sampler → save - you don't need this node, and you shouldn't add nodes for their own sake. Reach for it when the model wire has to cross a crowded part of the graph, or when you're wiring into a subgraph/collector setup and want a stable typed tap point that doesn't depend on node IDs. It's also handy for visually documenting the pipeline: a passer labeled "main model here" makes a shared workflow readable to the next person who opens it.

Install it

Ships in ComfyUI_Eclipse. ComfyUI Manager → search "Eclipse" → Install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Standard pack deps (opencv-python, pilgram, PyYAML, aiohttp; portable installs may need pip install -r custom_nodes/ComfyUI_Eclipse/requirements.txt). It's under Eclipse → Router → Typed.

Gotchas

The one thing to keep in mind: a passer passes the object reference, not a copy. If some other node downstream mutates the model (applying a patch or a LoRA in place), the change can be visible through the passer too - the passer isn't a snapshot. For 99% of workflows that's fine and even desirable, but don't treat a passer as an isolation barrier; it's plumbing, not a sandbox.